Closed Bug 657112 Opened 13 years ago Closed 13 years ago

Set KNOWN_LANGUAGES locally to KNOWN_LANGUAGES_PROD on the production server after the 1.0 push

Categories

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

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: stas, Assigned: jabba)

Details

(Keywords: l12y, Whiteboard: [5/16]) 

As per bug 656458, please change the value of KNOWN_LANGUAGES to KNOWN_LANGUAGES_PROD in settings.py on production when you push 1.0 out.

- KNOWN_LANGUAGES = KNOWN_LANGUAGES_DEV
+ KNOWN_LANGUAGES = KNOWN_LANGUAGES_PROD

This change should be made locally on the production server (while changes in bug 656458 happen in the upstream repo).  That's really the only reasonable way of having two values for this settings (one for dev and one for prod).  We'll trying to figure out a better way for the future projects.

Jabba, Corey -- let me know if you have any questions.  Also, should I move this into ServOps?

Thanks!
Assignee: nobody → cshields
Whiteboard: [5/16]
Assignee: cshields → server-ops
Component: markup.mozilla.org → Server Operations
Product: Websites → mozilla.org
QA Contact: markup-mozilla-org → mrz
Target Milestone: 1.0 → ---
Version: Firefox 4 → other
I'll write a patch to fix this more generally for the next release, and gandalf will write a temporary patch to just fix this issue on prod right now.
Is this actionable now? Let me know what I need to do.
Assignee: server-ops → jdow
No, we don't want to touch settings.py - it will get clobbered (like the last local patch did).  Closing this out pending a better solution.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.