Closed Bug 638990 Opened 14 years ago Closed 14 years ago

next.webowonder.allizom.org staging server

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: ozten, Assigned: fox2mike)

References

()

Details

Based on discussion between engagement, webdev, and webqa... we need a 2nd web o wonder staging server. This will host the 2.0 release which is a mobile version of the website. Details: Please setup the Django website * Just like webofwonder.allizom.org * Except webowonder repo should auto update from the mobile branch suggested domain: http://next.webowonder.allizom.org/
Summary: mobile.demos.allizom.org staging server → next.webowonder.allizom.org staging server
Spoke with MRZ about this and added corey to the bug.
(In reply to comment #0) > Based on discussion between engagement, webdev, and webqa... we need a 2nd web > o wonder staging server. > > This will host the 2.0 release which is a mobile version of the website. > > Details: > Please setup the Django website > * Just like webofwonder.allizom.org > * Except webowonder repo should auto update from the mobile branch > > suggested domain: http://next.webowonder.allizom.org/ Which is the mobile branch? Any setup instructions specific to this site? (I could muck around with the first one and figure out, but would be easier if you pointed me in the right direction).
Also, is the mobile site needed for the Fx4 launch?
Assignee: server-ops → shyam
(In reply to comment #2) > (In reply to comment #0) > > Based on discussion between engagement, webdev, and webqa... we need a 2nd web > > o wonder staging server. > > > > This will host the 2.0 release which is a mobile version of the website. > > > > Details: > > Please setup the Django website > > * Just like webofwonder.allizom.org > > * Except webowonder repo should auto update from the mobile branch > > > > suggested domain: http://next.webowonder.allizom.org/ > > Which is the mobile branch? Any setup instructions specific to this site? (I > could muck around with the first one and figure out, but would be easier if you > pointed me in the right direction). Austin can help with this one..(In reply to comment #3) > Also, is the mobile site needed for the Fx4 launch? We would like it to launch for fx 4 mobile launch, not desktop. Having said that, the sooner, the better.
(In reply to comment #4) > We would like it to launch for fx 4 mobile launch, not desktop. Having said > that, the sooner, the better. Sure. In the above case, this is not going to take priority over work for fx4, which there is lot of :) I wouldn't
work on it unless all the fx4 stuff is complete, sorry for that incomplete comment.
(In reply to comment #2) https://github.com/mozilla/webowonder is accessible from the 'mozillait' github user. This repo is public now, so maybe you don't care about mozillait. The branch is named 'mobile'. The setup is the same as http://webofwonder.allizom.org/ A quick rundown: 1) clone webowonder 1.1) copy settings_local.py from other stage 2) git checkout master 3) git clone --recursive webowonder-lib and name it vendor 4) svn checkout https://svn.mozilla.org/projects/l10n-misc/trunk/demos.mozilla.org/locale/ This should be a directory named locale 5) Run bin/update_site.py -e stage -v Verify it doesn't have an errors. The script minifies JS and CSS files. The script does database migrations. 6) put bin/update_site.py -e stage into a cron like the one on the other stage 6.1) put in a cron to svn update locale and then 'cd locale && ./compile_mo.sh .' This will keep this stage up to date. Please make cron identical to the other stage.
(In reply to comment #5) > (In reply to comment #4) > > > We would like it to launch for fx 4 mobile launch, not desktop. Having said > > that, the sooner, the better. > > Sure. In the above case, this is not going to take priority over work for fx4, > which there is lot of :) I wouldn't We understand, but we'd really like the site up live for mobile launch, which is march 21st.
We'll go ahead and stage this on the existing webofwonder.allizom.org. You can cancel this provisioning request.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.