Closed
Bug 519399
Opened 16 years ago
Closed 16 years ago
Run webroot/htaccess.sh on SUMO staging and discuss setting up a cronjob for it
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: paulc, Assigned: dmoore)
References
Details
We need webroot/htaccess.sh to run again on staging.
Since we seem to do this pretty often, we should discuss the possibility of adding a cron for it. It would be even better if the script would only run when it has changed since last run -- and perhaps we could modify on the dev side to make it so.
| Assignee | ||
Updated•16 years ago
|
Assignee: server-ops → dmoore
Comment 1•16 years ago
|
||
We also need it run on mobile.support-stage, while you're there.
| Assignee | ||
Comment 2•16 years ago
|
||
Run as requested.
Paul, the htaccess.sh is fairly lightweight. Is there any reason not to run it
after every svn update?
Comment 3•16 years ago
|
||
Derek, let's go ahead and run after every svn up. Definitely preferable to us filing bugs all the time.
| Reporter | ||
Comment 4•16 years ago
|
||
Yay!!
| Assignee | ||
Updated•16 years ago
|
Assignee: server-ops → dmoore
| Assignee | ||
Comment 6•16 years ago
|
||
We're going to need some provision to detect or lock the script to preserve manual changes, this should be figured out shortly.
I've run it again by hand, in the meantime.
| Reporter | ||
Comment 7•16 years ago
|
||
Derek: I tried to find you on #bmo, but I'll just post here: do you need anything from us on the dev end?
I think we would be happy if the script (webroot/htaccess.sh) ran whenever webroot/htaccess.dist changes, at least. If you can set it up to run when htaccess.dist in any folder changes, that would be even better.
Comment 8•16 years ago
|
||
(In reply to comment #6)
> We're going to need some provision to detect or lock the script to preserve
> manual changes, this should be figured out shortly.
How significant are the manual changes?
| Assignee | ||
Comment 9•16 years ago
|
||
The manual changes are quite rare, and generally just used for IT debugging. My intention was to specify a global lock file which the sysadmin could touch to prevent automatic updates while work is taking place. This should suffice, and it avoids the overhead of recursing through the tree and comparing timestamps on all the htaccess.dist files.
No dev support would be necessary, we'll just make it part of the script which pulls from SVN.
Thoughts?
Comment 10•16 years ago
|
||
That sounds fine to me. Then in those rare cases we might still need manual updates, if I understand you correctly, but the majority of the time we can just run the htaccess.sh after any svn update, right?
| Assignee | ||
Comment 11•16 years ago
|
||
James, correct. There will basically just be an override switch that sysadmins can throw to temporarily disable all automatic htaccess updates for debugging.
Comment 12•16 years ago
|
||
You've got my vote.
| Reporter | ||
Comment 13•16 years ago
|
||
+1 from me too.
| Assignee | ||
Comment 14•16 years ago
|
||
Automatic htaccess updates are now in place, running after every SVN update.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 15•16 years ago
|
||
Great! Thanks for all your help Derek.
Verified FIXED; bug 509881 relied on this change to show up, and it's been verified to work, which means this worked. Thanks again, Derek!
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•