Closed
Bug 1033548
Opened 10 years ago
Closed 8 years ago
Investigate using vagrant or docker for the dev environment
Categories
(Mozilla QA Graveyard :: One and Done, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rbillings, Unassigned)
Details
Attachments
(1 file)
46.02 KB,
image/png
|
Details |
Investigate using Heroku for the dev environment
Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
(In reply to Rebecca Billings [:rbillings] from comment #1) > Created attachment 8449648 [details] > account creation I think you attached this to the wrong bug.
Comment 3•10 years ago
|
||
Were we going to investigate a 3rd party hosting solution, or using vagrant, or both? The impression I got from the discussion was that we were only going to investigate the latter, but I could have been wrong.
Reporter | ||
Comment 4•10 years ago
|
||
Sorry the attachment is for another bug. Discussion was for investigating Heroku, but if it isn't a big time investment there's no reason not to look at both.
I favour first making a developer guide on the One and Done wiki to complement the github readme, at least for now. Down the line, we could do something like the Dreamwidth project's Dreamhack service. "The Dreamhack service is a hosted development sandbox environment where you can do Dreamwidth development without having to have your own server. Dreamhack accounts are available free of charge for anyone who's interested in working on the Dreamwidth code." http://wiki.dreamwidth.net/wiki/index.php/Dreamhack_Getting_Started
Chiming in to say I have a Vagrantfile and install script for One and Done (except for an SMTP server). I'm sure I break best practices all over the place, but it does encode everything that needs to be done from a base Ubuntu install. It might be useful as a starting point for something better and/or a wiki developer guide. I went ahead and pushed these to my fork: https://github.com/musicalchair/oneanddone/blob/vagrant/Vagrantfile https://github.com/musicalchair/oneanddone/blob/vagrant/install-vagrant.sh Let me know if there's any interest in taking this further or if there's a better way to do this!
Comment 7•10 years ago
|
||
Is it about running the oneanddone code in heroku? I can try that as I have heroku installed on my system now.
Comment 9•10 years ago
|
||
As discussed in the meeting this week, trying to get this running on Heroku is a very low priority, but getting a quick dev setup working with vagrant would be great. There are a number of other web dev projects that have already done this, and we should look to them for guidance and inspiration. One specific example is http://people.mozilla.org/~rhelmer/socorro-docs/development/dev-services.html#set-up-a-vm-with-vagrant
Summary: Investigate using Heroku for the dev environment → Investigate using vagrant for the dev environment
Target Milestone: Milestone 2 → Future
Comment 10•9 years ago
|
||
Some sites are using Docker for this, and others are using Vagrant. This bug, when taken, should start with an investigation of those options (and any others that seem worth investigating).
Summary: Investigate using vagrant for the dev environment → Investigate using vagrant or docker for the dev environment
Updated•9 years ago
|
Priority: P3 → P4
Updated•8 years ago
|
Target Milestone: Future → ---
Version: Version 2 → unspecified
Reporter | ||
Comment 11•8 years ago
|
||
Project is being retired.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•