On Sat, Aug 10, 2013 at 8:07 PM, Chad Perrin <[email protected]> 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. Additional Notes: * You can use whatever TCP port you want in place of 8888. * If you run the "fossil server" command as root, and if the directory containing repository files (and the repo files too) are owned by some non-root user, then Fossil will fork a copy of itself for each inbound request and put itself into a chroot jail as the user who owns the directory, before reading anything off of the wire. * The "fossil server" command actually runs an HTTP server which can serve static content if you use the right command-line options. * Users will have to log into each repository separately, by default. However, if you put multiple repos together into a "login group", then logging into one repo logs them into all other repos of the login group where they have an account. And changing passwords on one repo changes passwords on all repos where they have an account. Login-group set-up is under the "Admin" menu. > The > connection should be encrypted so that nobody can sniff usernames and > passwords when people are syncing, the users should preferably all be > using different credentials (not the same username/password combination, > in other words), and I should not have to pay any money to any third > parties (ISPs, certifying authorities, et cetera) as part of this. > > I've been playing with this a bit on the internal network for a couple > days, but I haven't come up with anything that really satisfies me yet. > Any help would be appreciated. > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
