Confirmed users
920
edits
Webdev:DevBoxVMImages: Difference between revisions
→Maintaining VM images
LesOrchard (talk | contribs) |
LesOrchard (talk | contribs) |
||
| Line 65: | Line 65: | ||
* Use <code>vagrant destroy && vagrant up</code> to spin up a VM in VirtualBox | * Use <code>vagrant destroy && vagrant up</code> to spin up a VM in VirtualBox | ||
* Build Puppet manifests to install packages and configure the VM with a running site | * Build Puppet manifests to install packages and configure the VM with a running site | ||
** If not Puppet manifests but tweaked by hand, then it will always need to be done by hand. | |||
** If automated by Puppet manifests or other scripts, then it can be run by machine | |||
** Do whatever is expedient, since the VM images are the important thing | |||
** Someday, it might be nice to steal whatever Puppet manifests IT uses, though. | |||
* Use <code>vagrant package</code> to extract a <code>{sitename}.box</code> image, once the site is verified to be running. | * Use <code>vagrant package</code> to extract a <code>{sitename}.box</code> image, once the site is verified to be running. | ||
* Upload the exported <code>{sitename}.box</code> image to hosting site for download. | * Upload the exported <code>{sitename}.box</code> image to hosting site for download. | ||