Hi all! Thank you all for such a great tool as fossil!
I've become big fan of the fossil SCM some time ago and past few days I spent finally moving fossil repositories to the production server (I need some sort of centralized hosting for all my stuff) and funny thing happened -- fossil let me down for the first time :) My setup look like this: ngnix reverse proxy, port 80 <-> apache daemon running fossil via CGI, port 8080 And since fossil sets absolute URL to all resources embedded... the people outside have seem my repositories wiki, tickets, and other filled with links to localhost:8080 I've looked in source code and found that it's a designed behavior of the fossil, and to make everything work for me I got to apply dirty hack cutting hostname and port number (as well protocol) from g.zBaseURL variable (and consequently from $baseurl variable used in html templates). The questions are: 1) Is there any other way around the setting up fossil behind reverse proxy without recompiling? 2) Should we consider using relative URLs instead of absolute? Isn't it a easier way of setting up fossil on the production environments? Many thanks in advance for your answers and for creating really useful tool! -- @macacq _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
