1063411 - Adjust treeherder .htaccess to serve the UI from the root directory not /ui/

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P1)

Description

[Ed Morley [:emorley]]

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.

Comment 1

[Ed Morley [:emorley]]

Raising priority since I think we should try and tackle this before we start linking to treeherder from too many places.

Comment 2

[Jonathan Eads ( :jeads )]

Attachment: Remove ui route

Comment 3

[Treeherder GitHub Bugbot]

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

Comment 4

[Ed Morley [:emorley]]

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?

Comment 5

[Ed Morley [:emorley]]

Mauro, aiui this needs a vagrant provision to pick the changes up - what's the best way forwards with this?

Comment 6

[Mauro Doglio [:mdoglio]]

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.

Comment 7

[Ed Morley [:emorley]]

Thank you - reopening bug so this appears on the wiki page until it's deployed.

Comment 8

[Ed Morley [:emorley]]

Filed bug 1088577 to run the vagrant provision, so the request is clearer & so we can close this out in the meantime.