You could make the release package a file in your project. Fossil would then be able to serve the file the same as it serves any other project file. However, this will add extraneous data to push/pull operations.
---> That sounds like a good idea. I'll try this approach as well. It seems even nicer than having to set up another web server and would keep things simple. Especially given the fact that I'm facing a problem now with running fossil using a CGI script. The problem is as follows: I can access the fossil website of my repo using http://localhost/cgi-bin/fossil.cgi but as soon as I try to create a wiki page for example I see just a blank page in the webbrowser (as soon as I entered the name I would like to have for the new wiki page and click on "create"). Same is true for ticket generation. When I try the same using "fossil ui" everything works fine. Could this be something related to access rights? My setup is now as follows: I use the simple webserver shown here http://www.sqlite.org/docsrc/artifact/0f78441e2de25641b0 It is started by xinetd using the following configuration: cat /etc/xinetd.d/althttp # default:on # description: This is the simple althttpd webserver daemon. service althttpd { disable = no type = UNLISTED socket_type = stream port = 80 protocol = tcp wait = no user = felix passenv = PATH server = /home/felix/ResourceManagement/Website/althttpd server_args = -logfile althttpd.log -root /home/felix/ResourceManagement/Website/www -user felix } The permissions of the files in the www subdir and especially the fossil repo seems OK to me: ll rmc.fossil -rw-r--r--. 1 felix felix 138240 23. Apr 11:22 rmc.fossil Any ideas about this? Am Freitag, den 22.04.2011, 18:04 -0400 schrieb Ron Wilson: > On Thu, Apr 21, 2011 at 5:14 PM, Felix Wolfheimer > <[email protected]> wrote: > > Thanks for your answer. To be more specific: It is no problem to write > > the download page manually. I don't expect fossil to do this for me. But > > when I have the download.html file plus the packages/installers/source > > archives or whatever things I would like to provide to the users: Where > > should I place them such that I can use the fossil built-in webserver to > > host them. Where are the files physically located such that the link in > > the download.html on the fossil website works correctly and points to > > the file? > > You could make the release package a file in your project. Fossil > would then be able to serve the file the same as it serves any other > project file. However, this will add extraneous data to push/pull > operations. > > (Does the auto-shun feature push/pull the shun data before file data?) > > Alternately, you could run a second instance of Fossil to serve the > release package. However, probably better to run a general purpose > webserver. > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
