On Tue, Aug 13, 2013 at 10:12 AM, David Mason wrote:
>
> All I want is for my users to say:
>
> fossil clone ssh://remote/proj.fossil clone.fossil
>
> or similar (without identifying any fossil user or password in the
> command - or prompted), and have ssh fire off a remote fossil based on
>
On Tue, Aug 13, 2013 at 8:55 PM, Andy Bradford wrote:
> But what if you want to
> have just a single SSH account to house all of your Fossils for a team?
>
FWIW: i found this feature sorely missing when i started using fossil, but
by the time it got SSH support i was so happy with CGI that i neve
Thus said David Mason on Tue, 13 Aug 2013 13:12:47 -0400:
> All I want is for my users to say:
>
> fossil clone ssh://remote/proj.fossil clone.fossil
>
> [snip]
>
> It appears that I can do that (possibly with a small auxiliary script)
> with the changes that Andy is working on.
You can pr
I've been trying to track the various options, particularly from Andy,
but being new to fossil, it might be easier to simply say what I need.
All I want is for my users to say:
fossil clone ssh://remote/proj.fossil clone.fossil
or similar (without identifying any fossil user or password in t
Thus said "Andy Bradford" on 11 Aug 2013 09:15:53 -0600:
> # will prompt for Fossil user otheruser but login to SSH using local
> USER fossil clone -h on -l otheruser ssh://remote//tmp/proj.fossil
> clone.fossil
I'm also considering dropping -h altogether, and making neither options
global
Thus said Stephan Beal on Sun, 11 Aug 2013 15:26:50 +0200:
> One of the devs (Andy?) has been working on integrating ssh forced
> commands with fossil so that ssh connections can use fossil's
> authentication. i'm not sure what the status of that is, but from what
> i've read it sound
6 matches
Mail list logo
