Vagrant - Environnements de dev
Find a file
2023-06-15 13:42:27 -07:00
.ci Terraform managed file 2023-06-15 08:47:09 -07:00
.github Handle skipped required tests 2023-06-12 14:24:21 -07:00
bin Use remote plugin module when in server mode 2022-04-25 12:26:13 -05:00
binstubs Updates to make vagrant-spec work in CI 2022-04-25 12:26:50 -05:00
builtin Add plugin example of coloring terminal output 2022-09-14 11:42:54 -04:00
cmd/vagrant Make no-op test work 2022-04-25 12:24:14 -05:00
contrib Make bash completion for "vagrant box add" patch by @ip1981 2022-10-19 17:02:23 -06:00
ext/vagrant_ssl Include libcrypto when linking 2023-05-31 08:48:13 -07:00
internal Use proto merge for merging proto based types 2023-06-12 09:33:00 -07:00
keys Use SSL and HTTPS links where appropriate 2016-01-25 13:14:54 -05:00
lib Generated proto updates 2023-06-05 14:18:06 -07:00
nix Update local dev to Ruby 3.1 2023-06-05 17:39:58 -07:00
plugins Project client and proc mapper fixes 2023-06-05 17:39:58 -07:00
scripts Release 2.3.0 2022-08-05 15:16:44 -07:00
tasks Change test:unit output format to documentation 2022-04-25 12:26:40 -05:00
templates Clarify missing library error 2023-06-12 16:45:42 -07:00
test Merge pull request #13194 from chrisroberts/ssh-comm-interactive 2023-06-02 17:14:23 -07:00
thirdparty/proto Update git submodule location 2022-04-25 12:26:25 -05:00
website Release 2.3.7 2023-06-15 13:40:35 -07:00
.envrc Adapt nix configs for Vagrant needs 2022-04-25 12:25:55 -05:00
.gitignore Update ignore file 2023-06-07 17:44:24 -07:00
.gitmodules Update git submodule location 2022-04-25 12:26:25 -05:00
.runner.sh Add simple build script 2018-03-07 08:52:53 -08:00
.vimrc .vimrc with vagrant tabstop settings 2013-10-22 08:24:58 +02:00
.yardopts YARD and some documentation 2010-09-22 09:43:30 -06:00
CHANGELOG.md Update files for new development 2023-06-15 13:42:27 -07:00
Dockerfile Add gogo 2022-04-25 12:23:57 -05:00
flake.lock Update local dev to Ruby 3.1 2023-06-05 17:39:58 -07:00
flake.nix Update dev tools 2023-06-05 14:18:05 -07:00
Gemfile Move to_proto to config classes 2022-04-25 12:24:21 -05:00
gen.go Add LoadLocation stringer generation 2022-06-15 11:15:08 -07:00
go.mod Update vagrant-go dependencies 2023-06-12 09:33:00 -07:00
go.sum Update vagrant-go dependencies 2023-06-12 09:33:00 -07:00
LICENSE Update LICENSE 2022-11-09 17:29:45 -08:00
Makefile Add a force-test target to disable caching 2023-06-12 09:33:00 -07:00
Rakefile Add helper for loading OpenSSL providers 2023-05-25 15:36:55 -07:00
README.md Add note about curl to README 2020-11-06 15:42:10 -08:00
RELEASE.md Update default branch to main 2020-10-19 16:37:10 -05:00
shell.nix Start with straight copy/paste from waypoint project 2022-04-25 12:25:55 -05:00
tools.go Update Makefile output location and update targets 2023-05-17 14:37:46 -07:00
vagrant-config.hcl Add gogo 2022-04-25 12:23:57 -05:00
vagrant-spec.config.example.rb core: Within a Bundler env, don't manage Bundler 2014-01-17 09:39:20 -08:00
vagrant.gemspec Add helper for loading OpenSSL providers 2023-05-25 15:36:55 -07:00
Vagrantfile Restore Vagrant development Vagrantfile 2022-07-28 14:12:50 -05:00
version.txt Update files for new development 2023-06-15 13:42:27 -07:00

Vagrant

Vagrant is a tool for building and distributing development environments.

Development environments managed by Vagrant can run on local virtualized platforms such as VirtualBox or VMware, in the cloud via AWS or OpenStack, or in containers such as with Docker or raw LXC.

Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.

Quick Start

Package dependencies: Vagrant requires bsdtar and curl to be available on your system PATH to run successfully.

For the quick-start, we'll bring up a development machine on VirtualBox because it is free and works on all major platforms. Vagrant can, however, work with almost any system such as OpenStack, VMware, Docker, etc.

First, make sure your development machine has VirtualBox installed. After this, download and install the appropriate Vagrant package for your OS.

To build your first virtual environment:

vagrant init hashicorp/bionic64
vagrant up

Note: The above vagrant up command will also trigger Vagrant to download the bionic64 box via the specified URL. Vagrant only does this if it detects that the box doesn't already exist on your system.

Getting Started Guide

To learn how to build a fully functional development environment, follow the getting started guide.

Installing from Source

If you want the bleeding edge version of Vagrant, we try to keep main pretty stable and you're welcome to give it a shot. Please review the installation page here.

Contributing to Vagrant

Please take time to read the HashiCorp Community Guidelines and the Vagrant Contributing Guide.

Then you're good to go!