Closed Bug 823062 Opened 11 years ago Closed 11 years ago

www.allizom.org translations not autoupdating from svn

Categories

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

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Assigned: nmaul)

References

(Blocks 1 open bug)

Details

It seems that the django part of allizom.org, our staging server for mozilla.org, is not autoupdating translations from svn.

Documentation says that it should update every 10mn:
http://bedrock.readthedocs.org/en/latest/contribute.html#server-architecture

Stage
URL: http://www.allizom.org/
PHP SVN branch: tags/stage, updated every 10 minutes
Bedrock locale SVN branch: trunk, updated every 10 minutes
Bedrock Git branch: master, updated every 10 minutes

In https://bugzilla.mozilla.org/show_bug.cgi?id=793754#c19 we can see that this is not (or no longer) the case.

Thanks!
Bug 818934 altered the auto-update mechanism for stage. The PHP SVN branch still auto-updates, but the django portion does not... it relies on someone to push the button in Chief.

We can still have the locale data auto-update, but I'm 99% sure this is insufficient by itself- I believe the django app also needs to be reloaded in order for it to notice locale data updates. The restarting is somewhat painful for automated testing, as it essentially takes down the site for ~10-30 seconds. If we can stomach that, we can have the app reload as well.

If there's some better way to get a django / mod_wsgi app to notice that the locale data has been updated, that would be good too. :)
(In reply to Jake Maul [:jakem] from comment #1)
> Bug 818934 altered the auto-update mechanism for stage. The PHP SVN branch
> still auto-updates, but the django portion does not... it relies on someone
> to push the button in Chief.

That's a problem for me as I can't push that button and people that can live in timezones not really compatible with mine.

> 
> We can still have the locale data auto-update, but I'm 99% sure this is
> insufficient by itself- I believe the django app also needs to be reloaded
> in order for it to notice locale data updates. 

AFAIK, prod does not need to be restarted to notice updates in translations and most of the time, my local install of Bedrock doesn't either, there is even a caching mecanism for lang files, maybe the caching is too agressive on stage (I think it is one minute caching on a default insytall), can we restablish the autoupdate to check that your assumption is correct? 


Thanks
I've set this up... waiting a bit to see if it seems to work... I think cron will be louder than necessary and may need some squelching.
Seems to be fixed. I see localizations on the stage servers with recent timestamps:

-rw-r--r-- 1 root root  7238 Dec 19 13:30 www.allizom.org-django/bedrock/locale/et/main.lang
-rw-r--r-- 1 root root  5722 Dec 19 13:30 www.allizom.org-django/bedrock/locale/et/newsletter.lang
-rw-r--r-- 1 root root 19739 Dec 19 05:21 www.allizom.org-django/bedrock/locale/fr/mozorg/contribute.lang
-rw-r--r-- 1 root root 14808 Dec 19 05:21 www.allizom.org-django/bedrock/locale/nl/mozorg/contribute.lang
Assignee: server-ops-webops → nmaul
Status: NEW → RESOLVED
Closed: 11 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.