On 1/18/16, Damien Sykes-Pendleton <[email protected]> wrote: > Hi there. > I may have missed these points when looking through the available > documentation, so forgive me if they are already covered somewhere. > 1. Can Fossil email its user list when a change has been made, for example > if there has been a new commit? I can’t see a setting for that in Fossil > itself, but I’m not sure if there is currently a way that isn’t exposed or > located in an obvious place.
There is not a built-in way to do this. But I believe others have figured out how to do it by adding TH1 scripts. Maybe somebody else can answer this better than me. > 2. I know you can restrict what a user does by way of the capability > settings, but can you restrict users only to a certain branch or number of > branches? So for example if someone was a tester and had no business with > the source material, could I restrict them to a branch called testers that > contained a binary version? Or even better can I restrict what files can be > downloaded by them? Any user that has write access can update any file. Any user with read access can read any file. Giving all users write access to files is not a problem, since nothing is ever deleted or overwritten. A complete audit log is maintained. So if a tester ever misbehaves and writes into something they should not have written into, you have all the evidence you need to prosecute the matter through administrative channels. This is a deliberate choice in the design of Fossil. > 3. How would I go about programatically extracting information or files from > a fossil repository? Is there a library for this or would I have to use the > Fossil source code as a guide? You can do that. Or there were low-level "fossil" command for extracting individual files, such as "fossil artifact". -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
