Confirmed users
920
edits
Webdev:DevBoxVMImages: Difference between revisions
→Open questions
LesOrchard (talk | contribs) |
LesOrchard (talk | contribs) |
||
| Line 9: | Line 9: | ||
TBD: Should this be in an etherpad? | TBD: Should this be in an etherpad? | ||
=== Image generation by hand or by machine? === | |||
* Starting by hand early to iron out process | |||
** Need to remember to update images on a regular basis | |||
* Switch to Jenkins or something else for nightly builds | |||
** How would this work? Seems resource intensive | |||
** See also: {{bug|670471}} - [tracker] set up jenkins job to export socorro vagrant VM | |||
=== Vagrantfile as part of project, or separate repo? === | |||
* MDN includes Vagrantfile in the main project. | |||
** https://github.com/mozilla/kuma/blob/master/Vagrantfile | |||
* Socorro has a separate socorro-vagrant project. | |||
** https://github.com/rhelmer/socorro-vagrant | |||
* Probably only matters to the person or process generating the VM image | |||
** Since we should take care of that rather than demanding contributor to do a full <code>vagrant up</code> | |||
=== Code on host or in VM? === | |||
* Vagrant wants to wrap a VM around a directory of source on the Host. | |||
* Better if the source for the project were <code>git clone</code>'ed inside the VM and shipped along with the image? | |||
** No more shared folder from host to VM. | |||
** Would need to install Samba inside VM to edit code from host. | |||
** Need to configure and use <code>git</code> or <code>svn</code> inside VM | |||
** Need instructions advising a <code>git pull</code> after initial boot-up | |||
=== Blank slate content === | |||
* Need to import / generate some sample data / content to make the site useful | |||
* Anonymized export from prod? | |||
*** Pretty dangerous | |||
* Randomized data | |||
** Need to be sure it's not entirely non-sensical | |||
* Synthetic test data | |||
** Need to hand-maintain | |||
== Participating sites == | == Participating sites == | ||