graphite cannot run outside / location

[Pierre Baillet]

Hardcoded paths make it very difficult to operated outside "/".

[Pierre Baillet (octplane)]

Partial fix at : http://http://bazaar.launchpad.net/~octplane/graphite/url_management/revision/608

Remains to fix:

- inject via javascript the current script url to update all ext.js callback urls
- find something to heal the datastore ( dashboard.js#925 seems to store the url of the graph in the DB) when graphite has a new home
- see If there are no hidden 404s (cli has not been tested/debugged).

[chrismd (chrismd)]

Generally it's preferable to run Graphite in a separate vhost. Is there a reason you cannot do that? Changing to relative url paths has been tried before and it broke things quite badly (infinite redirect loops among other things) so I reverted it. I'm not going to say I'm against doing this but I will say that for it to be integrated into trunk it has to be very thoroughly tested because the absolute url assumptions are pervasive throughout the codebase, it is a ton of tiny changes all over the place and that is a tricky thing to do safely. I am also not interested in implementing this myself so I am going to mark this as Triaged unless someone would like to take ownership and assign to themselves.