Closed
Bug 862950
Opened 11 years ago
Closed 11 years ago
Deploy login.webmaker.org on AWS
Categories
(Webmaker Graveyard :: DevOps, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: boozeniges, Assigned: jon)
References
Details
(Whiteboard: u=dev c=login p=1 s=2013w17)
Repo is here - https://github.com/mozilla/login.webmaker.org Are we good to go are are further fixes needed?
Flags: needinfo?(jon)
Assignee | ||
Comment 1•11 years ago
|
||
We want to move away from Redis, and into cookieSessions. I can deal with that
Flags: needinfo?(jon)
Reporter | ||
Comment 2•11 years ago
|
||
:jbuck - we've got a bug for that (at least for the redis/memcached part) that I'll add as a blocker.
Depends on: 861398
Assignee | ||
Comment 4•11 years ago
|
||
I'll fill out the application form for this
Assignee: nobody → jon
Status: NEW → ASSIGNED
Summary: Get login.webmaker.org deployed at login.rekambew.org → Deploy login.webmaker.org on AWS
Reporter | ||
Comment 5•11 years ago
|
||
I did this on Wednesday/Thursday.
Updated•11 years ago
|
Whiteboard: u=dev c=login p=1 s=2013w17
Assignee | ||
Comment 7•11 years ago
|
||
Tagged v0.0.2, this is ready to deploy.
Assignee | ||
Comment 8•11 years ago
|
||
Er, that's v0.0.1
Comment 9•11 years ago
|
||
My checklist for this app: https://github.com/mozilla/mofo_system_configurations/issues/92
Comment 10•11 years ago
|
||
NOT IN PROD! DO NOT RESOLVE!
Comment 11•11 years ago
|
||
http://login.mofostaging.net is up! LOG_LEVEL=debug PORT=80 SESSION_SECRET="I always eat cheetohs with no pants on" ALLOWED_DOMAINS="http://makeapi.mofostaging.net http://thimble-node.mofostaging.net http://webmaker.mofostaging.net" AUDIENCE=http://login.mofostaging.net MONGO_URL="mongodb://mongo-db.mofostaging.net:27017/loginwebmakers"
Comment 12•11 years ago
|
||
This is now up at http://login.mofostaging.net It is deployable via Jenkins. Logs: http://loggins.mofoprod.net:3000/streams/517833450daa7b25740001a6-login-staging/messages App slug: wmlogin (who knew, Ubuntu has a package called login heh) A couple to'do's on the way to prod - [ ] Add this app to New Relic (?) - [ ] Security review - [ ] Load test it a bit - [ ] Update logging to make it prettier. RESPONSE_CODE="200" for example - [ ] Add a health check - [ ] Add caching? Do we want CDN, assets loading from somewhere? - [ ] Do we need sticky sessions? How are sessions handled? We will then add all the prod infrastructure, monitoring, and alerting. Assinging to JBuck for those q's, those tasks, etc. Then, you tell me when it is ready to go to prod.
Assignee: johns → jon
Comment 13•11 years ago
|
||
Marking as closed. Lets file other bugs when we need to go to prod.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•