From Fedora Project Wiki
No edit summary |
|||
| Line 17: | Line 17: | ||
|- | |- | ||
|[https://github.com/fedora-infra/bodhi Bodhi] | |[https://github.com/fedora-infra/bodhi Bodhi] | ||
|style="background:#dff0d8; color:#3c763d"|Completed | |style="background:#dff0d8; color:#3c763d;"|Completed | ||
| Vagrant + Ansible setup of bodhi | | Vagrant + Ansible setup of bodhi | ||
|- | |- | ||
| | |[https://github.com/fedora-infra/mote/ mote] | ||
| | |style="background:#f2dede; color:#a94442;"|Not Started | ||
| | |https://github.com/fedora-infra/mote/issues/104 | ||
|- | |- | ||
| | | | ||
Revision as of 05:56, 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 |