On 2013-07-20 23:06, Andy Bradford wrote:
Hello,
I've been working on a simple fossil command that will integrate
with
SSH accounts where SSH keys are in use and wonder if there is a
formal
process for coming up with new subcommand names? Here is what I have
at
the moment:
$ fossil help gate
Usage: fossil gate ?FILENAME?
fossil gate ?FILENAME?
Scans filename for the requested fossil path found in the
SSH_ORIGINAL_COMMAND environment variable and runs
fossil http path if found.
If filename is not present, just run fossil http with the
requested path and the operating system will impose restrictions.
Any suggestions?
Thanks,
Andy
--
TAI64 timestamp: 4000000051eafbf8
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
I don not understand this.
A forced command is in place and it can only be fossil http.This will
check
if it is started via ssh and then look in the environment to see if
the request was fossil gate myotherdb.
what are you trying to archive?
--
Rene
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
