From Fedora Project Wiki
(Created page with "The aim of this page is to document the implementation of Vagrant for hacking on all Fedora web Applications. = Guidelines for Vagrant setups = * All Vagrant setups will use:...") |
No edit summary |
||
| Line 2: | Line 2: | ||
= Guidelines for Vagrant setups = | = Guidelines for Vagrant setups = | ||
1. All Vagrant setups will use: | |||
** vagrant-libvirt as the provider | ** vagrant-libvirt as the provider | ||
** vagrant-sshfs as the method for syncing files between the Guest and Host | ** vagrant-sshfs as the method for syncing files between the Guest and Host | ||
** ansible as the method of provisioning | ** ansible as the method of provisioning | ||
2. The Vagrantfile will be placed in the root directory of a project's repo, as a Vagrantfile.example, with instructions in the README to copy this to Vagrantfile, with Vagrantfile also being added to the .gitignore. This is so a developer can make small changes to the vagrant setup without polluting the main Vagrantfile.example in the repo. | |||
= Web Application conversion status = | |||
Revision as of 03:23, 27 September 2016
The aim of this page is to document the implementation of Vagrant for hacking on all Fedora web Applications.
Guidelines for Vagrant setups
1. All Vagrant setups will use:
- vagrant-libvirt as the provider
- vagrant-sshfs as the method for syncing files between the Guest and Host
- ansible as the method of provisioning
2. The Vagrantfile will be placed in the root directory of a project's repo, as a Vagrantfile.example, with instructions in the README to copy this to Vagrantfile, with Vagrantfile also being added to the .gitignore. This is so a developer can make small changes to the vagrant setup without polluting the main Vagrantfile.example in the repo.