Quick links Playground | Workstations | Samples | Boxes | Packer templates
Contents Overview | Getting started | Usage | Contributing | Resources
This repository contains Vagrant environments using VirtualBox for .NET development purposes.
If you are interested in building your own Vagrant boxes instead, check out the Packer templates repo.
Vagrant up is the new make build.
@choult
Vagrant is a tool for managing (virtual) development environments. By abstracting the management of virtual machines, it provides a way to consistently set up single or multi-machine environments in a hosting-agnostic way. Just type vagrant up and have the same setup ready in minutes anywhere. See the official introduction for more details and usage scenarios.
Follow these steps to get started:
- Install Vagrant and the following plugins:
- Install VirtualBox.
- Install the Chef Development Kit.
- Disable virtualization platforms other than VirtualBox. On Windows, disable Hyper-V, in case it is running.
These might have been the last few occasions you configured something manually, Vagrant will take care of the rest.
If you are not familiar with Vagrant yet, check out the official guide for an introduction, and the command-line reference for more details.
Then, according to your scenario, give one of the following configurations a try:
- Playground for quick experiments in isolation.
- Workstations for setting up your everyday development environment.
Of course, the above setups are not the only way to configure your environments. Here are some options to tune them for your needs:
- If you need small or temporary changes (e.g. change the available resources, install additional packages) for any of the above enviroments' machines, you can simply change the related configuration values. See the environments' pages for the available options.
- If you need completely different environments (e.g. set up a deployment environment for your project), you can simply reuse the custom boxes and build whatever configurations you like. See the samples for the most common scenarios.
Any feedback, issues or pull requests are welcome and greatly appreciated.
This repository could not exist without the following great tools: