Re: [fossil-users] Displaying documents
Hello I think you have only to use relativ links: I've probably missed something along the way but way back in the olden days of Fossil if you wanted to display a document that was in the repository you put in a link like this: [http://skunkworx.company.com/cgi-bin/Myproj.cgi/doc/tip/ProjDocs/MyDOCS /desc.pdf | Code Description (pdf) ] Replace it by [http:doc/tip/ProjDocs/MyDOCS/desc.pdf | Code Description (pdf) ] Best regards Wolfgang ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Repository-dependant cookies (D. Richard Hipp)
Sounds great, I'll give it a try, when the new version can be downloaded. Unfortunately i don't have a build environment. Many thanks Wolfgang ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Repository-dependant cookies
I do *not* want to turn Fossil into a general-purpose web server and replacement for Apache. That is not its purpose. We have to draw the line somewhere, and I propose to draw the line here. I completely agree. Stick to your knitting, as they say. Maybe someone who has need for this type of setup could write a quick tutorial on getting something like lighthttpd or something equally light weight and self-contained set up for local use. I completely agree too. At the moment, i'm using 2 fossil server instances to serve to repositories on a Windows Home Server on two different ports. I added http://urlrewriter.codeplex.com/ to my IIS-configuration and using the following rules to rewrite the URLs like in apache. After switching two the new multi-repository-server, i've only to modify the replacements rules. In the same way, i could add a list-repository-page, just by adding a corresponding rule. RewriteRule ^/fossilscm$ fossilscm/index [QSA,NC,R] RewriteRule ^/fossilscm(/?.*)$ http://servername:8001$1 [QSA,NC,P] RewriteRule ^/fossil$ fossil/index [QSA,NC,R] RewriteRule ^/fossil(/?.*)$ http://servername:8000$1 [QSA,NC,P] So i call http://servername/wiki And get http://servername:8000 Where my fossil repo lives :-) In the future, the rule 2 would be changed to RewriteRule ^/fossilscm(/?.*)$ http://servername:8000/fossilscm/$1 [QSA,NC,P] Many Thanks Wolfgang ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Repository-dependant cookies
Hello It's the same with Firefox 3. I think, the problem is the name of the cookie, requested by the fossil-server (running in server-mode, i didn't get it work with IIS/cgi :-( ). You should always add a repository specific extension(Hash of the repository path?) to the cookie-name, like mentioned in: Suppose the names of the repositories files are abc.fossil, def.fossil, ghi.fossil and so forth. Then to reach each repository, visit: http://localhost/abc http://localhost/def http://localhost/ghi And so forth. If this functionality were implemented, then the cookie names would be fossil_login_2F616263, fossil_login_2F646566, and fossil_login_2F676869. Should the repository-part of the URL be the first part of the filename, or should there be a configuration in the admin section to overwrite the default URL-part? I don't know :-) Though it's not a must have, i like the idea of one fossil.exe server instance serving multiple repositories. In this case, you need the above extension too :-) The combination of 1 single file repository 2 multiple repositories on the command-line 3 one directory on the command line would be ok for me. In case 2 and 3, i would prefer to send a 'directory listing forbidden', if someone request data for the root without giving a repository-path. The only case, when requesting data for the root would be the case 1 - or case 2, if a wildcard only returns one repository. A list of available repositories could be send too, but this should be configurable in the admin part with an option 'Send repository list OR send directory listing forbidden'. The cgi-variant could be expanded in the same way. The extension to the command-line of the server has to be copied to the 'cgi-file', containging the repository paths(multiple lines for different repositories or a special markup for a directory. Best regard Wolfgang ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Repository-dependant cookies
Hello I'm hosting more than one repository on a single machine. I have to logon everytime, when i change in my browser from one to another repository. Would it be possible to have a Login-Cookie for every repository? I think the Cookie-name should have a repository-dependend part. Thanks Wolfgang ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Please contribute Fossil skins or themes
Hi Attached you'll find a skin, i made - based on the default. It looks a little bit more like a normal windows program. I added the timeline-search form to the footer and reorganized the links in the header. Best regards Wolfgang fossil-skin.conf Description: Binary data ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
