Vagrant - Environnements de dev
Find a file
2022-08-08 10:10:27 +02:00
.ci Include extension on compressed asset 2022-08-05 18:40:32 -07:00
.github Add Ruby 3.1 to the CI 2022-08-08 10:10:27 +02: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 Support and honor the "primary" option for Command plugins 2022-07-27 11:36:04 -05:00
cmd/vagrant Make no-op test work 2022-04-25 12:24:14 -05:00
contrib Fixed typo 2021-10-28 21:59:30 +09:00
internal Warn users when using vagrant-go 2022-07-28 11:54:27 -05:00
keys Use SSL and HTTPS links where appropriate 2016-01-25 13:14:54 -05:00
lib Only patch fake_ftp when running tests 2022-08-02 10:44:07 -07:00
nix nix: Update protobuf & mockery to latest version 2022-06-03 14:28:40 -05:00
plugins Merge pull request #12785 from dustymabe/dusty-el9 2022-08-01 12:10:40 -05: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 Add error message for errors originating from a remote 2022-05-13 17:14:50 -05:00
test Only patch fake_ftp when running tests 2022-08-02 10:44:07 -07:00
thirdparty/proto Update git submodule location 2022-04-25 12:26:25 -05:00
website Update released version on website 2022-08-05 18:38:12 -07:00
.envrc Adapt nix configs for Vagrant needs 2022-04-25 12:25:55 -05:00
.gitignore gitignore: delve, solargraph, rubocop 2022-05-25 16:19:50 -05: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 2022-08-05 18:40:18 -07:00
Dockerfile Add gogo 2022-04-25 12:23:57 -05:00
flake.lock nix: Update protobuf & mockery to latest version 2022-06-03 14:28:40 -05:00
flake.nix Start with straight copy/paste from waypoint project 2022-04-25 12:25:55 -05: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 Tidy up go.mod 2022-08-03 11:23:07 -07:00
go.sum Tidy up go.mod 2022-08-03 11:23:07 -07:00
LICENSE Update year on LICENSE 2019-03-25 10:21:32 -07:00
Makefile Add 32 bit build target for linux 2022-08-03 10:41:33 -07:00
Rakefile Change symbols inside hashes to 1.9 JSON-like syntax 2014-05-22 12:35:12 -04: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
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 support for Ruby 3.1 2022-08-08 10:10:24 +02:00
Vagrantfile Restore Vagrant development Vagrantfile 2022-07-28 14:12:50 -05:00
version.txt Update files for new development 2022-08-05 18:40:18 -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!