Closed
Bug 1063411
Opened 10 years ago
Closed 10 years ago
Adjust treeherder .htaccess to serve the UI from the root directory not /ui/
Categories
(Tree Management :: Treeherder, defect, P1)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: jeads)
References
Details
Attachments
(1 file)
Currently the treeherder UI is served out of:
https://treeherder.mozilla.org/ui/
eg:
https://treeherder.mozilla.org/ui/index.html
https://treeherder.mozilla.org/ui/css/index.min.css
...maps to this on production/staging (the grunt build output):
https://github.com/mozilla/treeherder-ui/blob/master/dist/index.html
https://github.com/mozilla/treeherder-ui/blob/master/dist/css/index.min.css
...and this for dev (the unminified source):
https://github.com/mozilla/treeherder-ui/tree/master/webapp/app/index.html
https://github.com/mozilla/treeherder-ui/tree/master/webapp/app/css/index.css
In order to help with bug 1042737, it would be great to serve the above assets out of:
treeherder.mozilla.org/
rather than:
treeherder.mozilla.org/ui/
By adjusting the rewrites in the .htaccess (or wherever) for dev, staging and production.
Reporter | ||
Comment 1•10 years ago
|
||
Raising priority since I think we should try and tackle this before we start linking to treeherder from too many places.
Priority: P2 → P1
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jeads
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8497889 -
Flags: review?(mdoglio)
Updated•10 years ago
|
Attachment #8497889 -
Flags: review?(mdoglio) → review+
Comment 3•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/treeherder-service
https://github.com/mozilla/treeherder-service/commit/5fd276b12db0993cb9f9e5a9f510ff5b3d2ad8c2
Bug 1063411 - Remove ui route
https://github.com/mozilla/treeherder-service/commit/a325589536d252b63f898966dc1ff5ca23730578
Merge pull request #234 from mozilla/bug-1063411-remove-ui-route
Bug 1063411 - Remove ui route
Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•10 years ago
|
||
jeads: So I can run vagrant provision on dev/stage to pick this up? What about prod - guessing IT need to run it? Could you coordinate with them?
Flags: needinfo?(jeads)
Reporter | ||
Comment 5•10 years ago
|
||
Mauro, aiui this needs a vagrant provision to pick the changes up - what's the best way forwards with this?
Flags: needinfo?(mdoglio)
Comment 6•10 years ago
|
||
You need to run vagrant provision to apply the changes to your environment.
I'll re-run puppet on dev and stage and see if everything is cool. We need fubar to apply the changes on production.
Flags: needinfo?(mdoglio)
Flags: needinfo?(jeads)
Reporter | ||
Comment 7•10 years ago
|
||
Thank you - reopening bug so this appears on the wiki page until it's deployed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•10 years ago
|
Assignee: jeads → nobody
Reporter | ||
Comment 8•10 years ago
|
||
Filed bug 1088577 to run the vagrant provision, so the request is clearer & so we can close this out in the meantime.
Assignee: nobody → jeads
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•