If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Deploy Django rewrite of Drumbeat.org

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Other
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: paulosman, Assigned: zandr)

Tracking

Details

(URL)

(Reporter)

Description

7 years ago
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.
(Reporter)

Updated

7 years ago
Depends on: 624717

Updated

7 years ago
Assignee: server-ops → zandr
(Reporter)

Comment 1

7 years ago
This has been done.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.