Hello all!

I'm currently using fossil in a way which I think is somewhat
nonstandard, but had a feature request that could potentially be useful
to others as well.

Rather than having a central, pseudo-public facing process, we are using
fossil exclusively behind SSH.  There is a shared account
([email protected]) with PKI, and we all have default user accounts to
track changes (fossil user default xxx).  The reason for this is that
the codebase is sensitive, and we prefer to keep services behind
ipsec/ssh when possible.  Fossil supports ssh pretty well, so we
determined this is easier for some of our non-technical users to get up
and running.

For developers, this process works great.  Autosync performs flawlessly,
and we go about our business.  However when filing tickets through the
UI, a "fossil sync" seems to be mandatory.  My request is that tickets
also get pushed via an autosync function on changes.

Also, I was pleasantly surprised to find that fossil has a
statically-linked flavor on OpenBSD, which makes it trivial to chroot
via ssh.  We have had nightmares in the past trying to do this with git
(why does it need /dev/random access!?, and no, git-shell doesn't count).

Thanks everyone who helped make fossil possible.  We have quite enjoyed
it thus far :)
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to