Closed
Bug 645150
Opened 14 years ago
Closed 14 years ago
make slavealloc-staging a bit more distinct
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
(Whiteboard: [slavealloc])
Attachments
(1 file, 1 obsolete file)
|
3.14 KB,
patch
|
bear
:
review+
dustin
:
checked-in+
|
Details | Diff | Splinter Review |
Currently, nginx serves slavealloc-staging on a different port, but uses the same /tools/slavealloc symlink. This precludes staging changes to the JavaScript/CSS, which will probably change frequently. It also precludes running staging and production from different revisions.
While I'm at it, I'd like to have a script that I can run to dump the staging db and copy the production db over to it.
|
Assignee | |
Updated•14 years ago
|
Whiteboard: [slavealloc]
|
|
Assignee | |
Comment 1•14 years ago
|
||
Change the nginx link, and add a few handy scripts. I created /tools/slavealloc-staging by hand on the server (documented in https://wiki.mozilla.org/Applications/Slavealloc).
Attachment #521954 -
Flags: review?(bear)
|
|
Assignee | |
Comment 2•14 years ago
|
||
and as usual, I forgot something in the patch
This adds a change to the slavealloc-staging initscript so that it uses the right symlink.
Attachment #521954 -
Attachment is obsolete: true
Attachment #521954 -
Flags: review?(bear)
Attachment #521955 -
Flags: review?(bear)
|
||
Updated•14 years ago
|
Attachment #521955 -
Flags: review?(bear) → review+
|
|
Assignee | |
Updated•14 years ago
|
Attachment #521955 -
Flags: checked-in+
|
|
Assignee | |
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•