Re: [fossil-users] How to share a fossil repo using static http (without the cgi)?
On 13/12/17 18:02, Warren Young wrote: On Dec 12, 2017, at 12:33 PM, Juan Francisco Cantero Hurtadowrote: I want share a fossil repo using a static http server Call something like this from a crontab: $ wget -O /var/www/html/dl/my-project.zip http://localhost:8080/zip Then in the HTML: Download I want share only the "code part" without the wiki or the issues. Fossil-produced zip files and tarballs leave that out. The main downside is that you don’t get delta downloads. The user would have to download the whole thing all over again. without the cgi. CGI isn’t necessarily required to run a Fossil web server. I understand that some web hosts don’t allow easy access to CGI for security reasons, but you might still be able to run a Fossil instance there with “fossil server” and use its HTTP server, possibly on a nonstandard port >= 1024. Then point the static pages to the Fossil instance: http://server-name:8080/zip/my-project.zip?uuid=trunk”>Download You do unfortunately have to give an absolute URL here: HTML doesn’t allow you to say “same server but different port,” on purpose, presumably for some security reason. The default permissions on Fossil allow anonymous users to download zip files and tarballs. Or, you could just expose the Fossil server publicly but deny anonymous users the ability to read tickets an the wiki. Then you get delta syncing and all the other Fossil goodness. Thanks guys for the help. -- 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
Re: [fossil-users] How to share a fossil repo using static http (without the cgi)?
On Dec 12, 2017, at 12:33 PM, Juan Francisco Cantero Hurtadowrote: > > I want share a fossil repo using a static http server Call something like this from a crontab: $ wget -O /var/www/html/dl/my-project.zip http://localhost:8080/zip Then in the HTML: Download > I want share only the "code part" without the wiki or the issues. Fossil-produced zip files and tarballs leave that out. The main downside is that you don’t get delta downloads. The user would have to download the whole thing all over again. > without the cgi. CGI isn’t necessarily required to run a Fossil web server. I understand that some web hosts don’t allow easy access to CGI for security reasons, but you might still be able to run a Fossil instance there with “fossil server” and use its HTTP server, possibly on a nonstandard port >= 1024. Then point the static pages to the Fossil instance: http://server-name:8080/zip/my-project.zip?uuid=trunk”>Download You do unfortunately have to give an absolute URL here: HTML doesn’t allow you to say “same server but different port,” on purpose, presumably for some security reason. The default permissions on Fossil allow anonymous users to download zip files and tarballs. Or, you could just expose the Fossil server publicly but deny anonymous users the ability to read tickets an the wiki. Then you get delta syncing and all the other Fossil goodness. ___ 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] How to share a fossil repo using static http (without the cgi)?
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"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
[fossil-users] How to share a fossil repo using static http (without the cgi)?
Something like: https://git-scm.com/book/en/v1/Git-Internals-Transfer-Protocols#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