In short, no. To be able to clone, fossil needs a server process of some sort, which means either CGI or a the built-in standalone http server. It can use SSH, but that uses fossil's built-in server to do the real work.
PS: the db does not store raw user passwords, but does store hashes of those passwords. ----- stephan Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting. On Dec 12, 2017 20:55, "Juan Francisco Cantero Hurtado" <i...@juanfra.info> wrote: > Something like: > > https://git-scm.com/book/en/v1/Git-Internals-Transfer-Protoc > ols#The-Dumb-Protocol > > https://www.mercurial-scm.org/wiki/StaticHTTP > > IIUC, the .fossil files include the users passwords and I don't know if > those include more private info. So, I can't just share directly the file. > > Let me give you an example, so it's more clear. I want share a fossil repo > using a static http server, without the cgi. And I want share only the > "code part" without the wiki or the issues. The user could clone the repo > and pull regularly the changes. Can I do something like that with fossil?. > > Cheers. > > > -- > Juan Francisco Cantero Hurtado http://juanfra.info > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
