On Thu, Apr 21, 2011 at 5:14 PM, Felix Wolfheimer <f.wolfhei...@googlemail.com> 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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
