Hi, I've been trying to implement a webservice that hosts fossil repositories. Kinda like chiselapp.com . I have achieved running my own server app written in golang to make the CGI requests in a routed handler (i.e /user/repository ), but the problem I'm facing is that the only way I can make it work is if a cgi script exists to pass as argument to fossil.
Is there any way around this? Like setting the repository or directory in an environment variable or something? You can understand that I don't want having lots of CGI scripts around when I could just ask the database and call fossil through cgi direclty, reading through 1 or 2 line cgi scripts dosn't seem much, but it is unecessary for a service like this (creating the scripts for each user/repo setting file permissions, etc...) when I can just point fossil where the directory or repository is. I do know CGI conventions and standards do not work like that, but is there something I don't know about fossil? Is there a way to request a feature to do this? This will boost a lot the potential of running fossil repositories behind dynamic applications. Thanks to everyone for your wisdom and guidance in this matter. Sincerely, Guillermo Estrada -- "No le digas a Dios lo grande de tu tormenta, mejor dile a tu tormenta lo grande que es tu Dios."
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
