Closed Bug 659419 Opened 14 years ago Closed 14 years ago

Changes for Markup on dev, stage, and production

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wenzel, Unassigned)

Details

Please make the following changes to the three Markup instances. Dev: - add setting to settings_local: ENABLE_RAW_MARKS = False Stage: - add setting to settings_local: ENABLE_RAW_MARKS = False - update code and run(s) migrations Prod: - take DB dump of current state. - add setting to settings_local: ENABLE_RAW_MARKS = False - update code, run(s?) migrations. - take a DB dump of that state. - hook up a vhost to allow load testing - tell mbrandt that it's ready to go and tell him how to access it
On stage, we also need to ensure that submissions from different clients end up with different IPs in the database. Let us know when you've updated this, so we can throw some marks at this. Then you should pull out the latest IPs from the DB to see if they differ.
Done, done and done. mcoates - you can start testing on markup.allizom.org or markup-dev.allizom.org (auto-updating). I gave mbrandt the correct /etc/hosts and domain name to use to test on production.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.