Re: [fossil-users] Automating a clone - any other way than the URL to pass in password?

On Sat, Jul 05, 2014 at 10:19:54AM -0700, Matt Welland wrote: > I'd like to automate a clone but I think I'd prefer the password not be in > the URL. The concern is that the password in the URL might be visible in > the webserver logs. Passwords are not passed in the request via URL, but as part o

[fossil-users] artifacts received

What are the "artifacts received" below? Is these administrative, or is there something else at play? myhost$ fossil pull Pull from http://joeb...@fossil-scm.org Round-trips: 1 Artifacts sent: 0 received: 74 Pull finished with 442 bytes sent, 2308 bytes received myhost$ fossil pull Pull from ht

[fossil-users] Automating a clone - any other way than the URL to pass in password?

I'd like to automate a clone but I think I'd prefer the password not be in the URL. The concern is that the password in the URL might be visible in the webserver logs. First, is this a legit concern? Second, how best to do this? AFAICT there is no switch for fossil to take the password in on stdin