Closed
Bug 624710
Opened 14 years ago
Closed 13 years ago
Deploy Django rewrite of Drumbeat.org
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: paulosman, Assigned: zandr)
References
()
Details
Once the final blockers have been resolved, and security review has been done, we'd like to deploy the new, rewritten drumbeat.org. We'll also need to keep the old drumbeat.org site around for a limited time. Here's the rough plan as I see it: 1) Create an A record or CNAME for old.drumbeat.org (or equivalent domain name, I'm not picky about this at all) to point to the existing drumbeat.org site (63.245.217.39). 2) Modify Apache Vhost config on existing drumbeat.org server and add 'old.drumbeat.org' as an alias. 3) Clone the VM we're using for staging. Modify apache config, add drumbeat.org as the ServerName for the vhost. 4) Modify A record for drumbeat.org / www.drumbeat.org to point at new VM.
Updated•13 years ago
|
Assignee: server-ops → zandr
Reporter | ||
Comment 1•13 years ago
|
||
This has been done.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•