I am in the process of getting fossil to run on my NAS devce, a DLink DNS-323. This beast is an ARM core running linux hosting a RAID made of two 1.5TB SATA drives, and with a cross toolchain in place under Ubuntu it was straightforward to get fossil to run there. However, the DNS-323 already has a web server on port 80 that provides all of its management UI, which is apparently not particularly extensible so it doesn't look easy to just add a CGI script to launch fossil with it.
So I got thttpd built and running on the DNS-323, and set it up so that fossil can be run via a simple CGI naming a specific repository. Now my URLs look like http://192.168.1.150:8080/r.cgi/example/index assuming that r.cgi points to a directory containing example.fossil. However, when I fetch that page, all of the links it contains are missing the port number. It is also unstyled and missing its logo because those links too are missing the port number. Oddly, just using "fossil server -R /mnt/HD_a2/repos" to launch a server for my repo collection returns pages that do include the port number in the links. I don't want to do that in my NAS, however, because that won't permit me to host a directory of available repositories or any files outside of revision control. My investigation got stalled after finding that g.zBaseURL is really missing the port number. From inspection of set_base_url() in main.c, it isn't obvious how "fossil server" is able to get this right in the first place. Any thoughts? Ross Berteig [email protected] Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 +1 626 351 1590 FAX _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
