user avatar
Update generated ssh private key file permissions on create
Chris Roberts authored
This updates the permissions on the automatically generated private
key file to only be readable by the user. Includes support for file
permission modification on Windows platform.
a69ff505
Name Last commit Last update
.github Update URLs for the repo
bin Spelling fixes
contrib Include explicit start to ensure start
keys Use SSL and HTTPS links where appropriate
lib Update generated ssh private key file permissions on create
plugins Update generated ssh private key file permissions on create
scripts Update RELEASE
tasks Use color
templates Merge pull request #9504 from zachflower/feature/vagrant-aliases
test Update generated ssh private key file permissions on create
website Merge pull request #9504 from zachflower/feature/vagrant-aliases
.gitignore Add a custom path location to ignore
.runner.sh Add simple build script
.travis.yml [CI] Test against Ruby 2.5
.vimrc .vimrc with vagrant tabstop settings
.yardopts YARD and some documentation
CHANGELOG.md Update CHANGELOG
Gemfile Update URLs for the repo
LICENSE Update license year
README.md Updating README.md with #vagrant IRC channel information.
RELEASE.md Propose fix some typos
Rakefile Change symbols inside hashes to 1.9 JSON-like syntax
Vagrantfile Updated Vagrantfile to install more recent versions of software.
vagrant-spec.config.example.rb core: Within a Bundler env, don't manage Bundler
vagrant.gemspec Update generated ssh private key file permissions on create
version.txt

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

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/precise32
vagrant up

Note: The above vagrant up command will also trigger Vagrant to download the precise32 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 the Gem from Git

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

Contributing to Vagrant

To install Vagrant from source, please follow the guide in the Wiki.

You can run the test suite with:

bundle exec rake

This will run the unit test suite, which should come back all green! Then you're good to go!

If you want to run Vagrant without having to install the gem, you may use bundle exec, like so:

bundle exec vagrant help

Acceptance Tests

Vagrant also comes with an acceptance test suite that does black-box tests of various Vagrant components. Note that these tests are extremely slow because actual VMs are spun up and down. The full test suite can take hours. Instead, try to run focused component tests.

To run the acceptance test suite, first copy vagrant-spec.config.example.rb to vagrant-spec.config.rb and modify it to valid values. The places you should fill in are clearly marked.

Next, see the components that can be tested:

$ rake acceptance:components
cli
provider/virtualbox/basic
...

Then, run one of those components:

$ rake acceptance:run COMPONENTS="cli"
...