On Sat, Aug 10, 2013 at 08:45:31PM -0400, Richard Hipp wrote: > On Sat, Aug 10, 2013 at 8:07 PM, Chad Perrin <c...@apotheon.net> wrote: > > > > So . . . let's say I have a server (running FreeBSD, and I'll probably > > be setting this up in a jail) and a router that can forward ports > > (already has SSH forwarded to this server). For argument's sake, let's > > say we're confined to only one port per protocol. What's the quick/easy > > way to get Fossil set up so a small team can push/pull/sync multiple > > Fossil repositories on the server without having shell accounts? > > > (1) Put all of the Fossil repositories you want to share in a single > directory, say "/home/fossil/repos". Make sure all repository files are > named using the *.fossil pattern. (Technically, you can scatter the > repositories out in a directory hierarchy, but let's keep things simple for > now.) > > (2) Run "fossil server -port 8888 /home/fossil/repos" > > (3) Users connect to "http://freebsdhost:8888/repo"; where "freebsdhost" is > the name of your server obviously, and where "repo" is the name of one of > your repositories with the ".fossil" suffix omitted.
If I'm not mistaken, this will *not* in fact use an encrypted connection to protect logins from network sniffing (such as when working from a coffee shop wireless network) for syncing with the command line interface of Fossil SCM. Is that correct? If so, I'm afraid that is not going to work for my needs. I am curious about some of the other things you mentioned in the email, and would like to look into them and perhaps ask more questions about them, but for now I want to focus on whether this solution is actually suitable to my needs at all. Thank you for the prompt response. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
