On 4/25/16, Matthieu Dubuget wrote:
>
> From my other tests, it seems that if the user who is cloning the repository
> has 'a' capability,
> he does not need to pull any additionnal configuration, to have a
> functionnal ticket system
> cloned, and able to push tickets modifications.
>
You should
On Apr 25, 2016 4:21 PM, "Matthieu Dubuget"
wrote:
>
> Le 25/04/2016 15:46, Stephan Beal a écrit :
> >
> > Might be misremembering, but don't the ticket schemas count as "config"
areas which need to be pulled once?
> >
>
> If you mean :
>
> ./fossil-1.34 configuration pull all http://test@srvif:80
Le 25/04/2016 15:46, Stephan Beal a écrit :
>
> Might be misremembering, but don't the ticket schemas count as "config" areas
> which need to be pulled once?
>
If you mean :
./fossil-1.34 configuration pull all http://test@srvif:8085
It is the last test I did in the listing you quoted. Or is it
On 4/25/16, Stephan Beal wrote:
> Might be misremembering, but don't the ticket schemas count as "config"
> areas which need to be pulled once?
They get pulled automatically on a clone. After the initial clone,
then you have to do "fossil config pull ..." for updates.
The bitmask in the second
Might be misremembering, but don't the ticket schemas count as "config"
areas which need to be pulled once?
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Apr 25, 2016 12:35 PM, "Matthieu Dubuget"
wrote:
> Hello,
>
> I have a fossil
Le 25/04/2016 13:58, Matthieu Dubuget a écrit :
> matt@xps:~/projets/bmts$ ssh srvif ./fossil-1.34 user capabilities test -R
> bugsMetalscan.fossil
> qjr
Oh. Sorry. For some reason, I put 'q' instead of 'g'!
'g' allows to clone.
But as in my initial e-mail, the ticket table is not cloned. I trie
Le 25/04/2016 12:55, Richard Hipp a écrit :
> On 4/25/16, Matthieu Dubuget wrote:
>> I had to add "g Clone: Clone the repository" capability to allow users to
>> clone the repository on their own computer. It seems logical.
>> Here are the capabilities of my test user : bceghjnprw
>>
>>
>> But it
On 4/25/16, Matthieu Dubuget wrote:
>
> I had to add "g Clone: Clone the repository" capability to allow users to
> clone the repository on their own computer. It seems logical.
> Here are the capabilities of my test user : bceghjnprw
>
>
> But it seems it is not enough: when `fossil ui` is starte
Hello,
I have a fossil repository which is used only for tickets, and is
served on our intranet: users are using it through the web ui only.
The goal would be that users could go out of the society with
a copy of the database, fill new tickets directly on their computer, and
synchronise
their mo
9 matches
Mail list logo
