On 7-8-2014 21:47, Will Parsons wrote:
Andy Bradford wrote:
Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
Since I wasn't transmitting any sensitive data anyway, I answered yes,
and then got:
Error: not authorized to write
Is there something wrong with the way I'm trying to authe
Andy Bradford wrote:
> Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
>
>> fossil push https://chiselapp.com/user//repository/ -B
>> ':'
>>
>
> By the way, if chiselapp does support HTTP_AUTH, then you might simply
> need to enable REMOTE_USER support in your respository if that
Andy Bradford wrote:
> Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
>
>> Since I wasn't transmitting any sensitive data anyway, I answered yes,
>> and then got:
>>
>> Error: not authorized to write
>>
>> Is there something wrong with the way I'm trying to authenticate?
>
> I see you
Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
> fossil push https://chiselapp.com/user//repository/ -B
> ':'
>
By the way, if chiselapp does support HTTP_AUTH, then you might simply
need to enable REMOTE_USER support in your respository if that is how
you prefer to authenticat
Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
> Since I wasn't transmitting any sensitive data anyway, I answered yes,
> and then got:
>
> Error: not authorized to write
>
> Is there something wrong with the way I'm trying to authenticate?
I see you used -B for HTTP_AUTH. I do
I'm trying out chiselapp for the first time and running into
difficulties. I managed to create an account for myself and upload an
existing repo successfully, but I can't seem to figure out how to push
changes to chiselapp.
What I thought should work is:
fossil push https://chiselapp.com/user//r
6 matches
Mail list logo
