Closed Bug 894566 Opened 12 years ago Closed 12 years ago

Set up a tool to temporarily deploy branches for design review

Categories

(Webmaker Graveyard :: DevOps, defect)

Product:
Webmaker Graveyard
Component:
DevOps
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kate, Assigned: johns)

References

Details

We need a way for members of our team without the local dev environment setup to test branches in progress interactively. This is pretty essential to getting design review for something that's in progress. This is our ideal list of asks: - temporarily deploy any branch and get a unique URL - be able to deploy more than one branch at a time - configure environment variables for testing for each branch (e.g. using the production makeapi endpoint, so we have real content to test with) - update deployed branch with new commits as changes are made Does this sound doable?
At this time, I don't really have the ability to easily do this for you guys. We have two potential options which are pretty fast though. 1) Use Heroku for these. https://blog.heroku.com/archives/2013/6/27/heroku-fork They have launched fork, which is a great way to tackle this need. 2) Setup dev servers on aWS for you folks who need to push to stuff like this.
Heroku works, but currently breaks as .env is not a part of our repo, and the app needs .env to run. Thoughts on how to get around this (perhaps read from env.dist if .env is not available to use defaults).
Sure, we can even set this up on jenkins.mofoprod.net as a job that will place that file from s3 or elsewhere into the correct position prior to deploying, bet.
Looking at a combination of docker and AWSbox(talking to lloyd about adding some functionality in for that!). I also have a cloudformation/docker/vagrant-compatible setup I am working on after Re:Invent.
Assigned to :jp, since he's actively working on this
Assignee: jon → johns
Status: NEW → ASSIGNED
Yeah, I've been chin rubbing all week on how to get this done in a vagrant box. I think I have a holiday solution, but I'm going to test it first. :) Happy Thanksgiving.
We have localdev vagrant completely set, but are now working on vagrant for AWS provider (to start).
Depends on: 964284
With the help of Hamabama, we have a webmaker-suite vagrant setup to use AWS as a provider. https://github.com/mozilla/webmaker-suite/tree/master/vagrant/aws I'd like to do this with other apps, of course, and the tooling (vagrant, etc) is there. I'm going to pump my fist and close this bug!
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.