Reinier Balt wrote:
I did find one issue with the proxying - if I used anything other than
"/" as the proxy path, anything addressed in tracks other than the
frontpage wouldn't load (including images, and all tasks, projects,
etc). This meant that I have to bind it to a weird port (81 here),
since
I use 443 to provide the "normal" https services on this box.
[zap]
Ideally I'd use:
ProxyPass /tracks http://127.0.0.1:3000/
ProxyPassReverse /tracks http://127.0.0.1:3000/
You need to tell tracks that it's running in a subdir or all url's that
are generated by tracks are wrong.
In RC2 this is quite easy, just uncomment the subdir entry in site.yml
Reinier
That's working really well for me now - thanks Reinier.
Only one slight issue - when I hit the login button, I get redirected to
https://my.host/ - rather than https://my.host/tracks. Apart from that,
it's working great!
Any thoughts on that?
--
--
Dr Orlando Richards
Information Services
IT Infrastructure Division
Unix Section
Tel: 0131 650 4994
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
