From Fedora Project Wiki
| Line 24: | Line 24: | ||
|https://github.com/fedora-infra/mote/issues/104 | |https://github.com/fedora-infra/mote/issues/104 | ||
|- | |- | ||
| | |[https://github.com/fedora-infra/mirrormanager2/ MirrorManager2] | ||
| | |style="background:#fcf8e3; color:#8a6d3b;"|In Progress | ||
| | |[https://github.com/fedora-infra/mirrormanager2/pull/191 pull request] -- still need to figure out how to create some sample data or do an import of the prod db into the testing instance | ||
|- | |- | ||
|} | |} | ||
Revision as of 06:53, 5 October 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.
Web Application conversion status
| App | Status | Notes |
|---|---|---|
| Bodhi | Completed | Vagrant + Ansible setup of bodhi |
| mote | Not Started | https://github.com/fedora-infra/mote/issues/104 |
| MirrorManager2 | In Progress | pull request -- still need to figure out how to create some sample data or do an import of the prod db into the testing instance |