Thus said "Michael L. Barrow" on Thu, 04 Dec 2014 13:34:42 -0800:
> What I'm trying to do is document the process of creating a new > repository that will be in the same login group of a master repo. From > my understanding, you still need to have the user accounts created in > the secondary repos even if they're in the same login group. I haven't played much with login groups, but in my experimentation with the web UI it seems that if you add a user in one repository, it has an option called Scope that allows you to apply it to all the repositories in the login group. If you check that option, when changing the user, it will take effect in all repositories in the group. I don't know if there is a similar Scope option when managing users from the command line, but it seems like for a login group, just using the UI will work. > Is there a better best practice for doing this? I would suggest using fossil config export/import user but I think I've misused it, or found a bug. I did ``fossil config export user fossil.users'' and then used ``fossil config import fossil.users'' in another repository and all users but the 2 listed in the fossil.users file were wiped out of the target repository. The problem I see with this is that it wiped out anonymous, developer, nobody, reader and the default setup user initially created from the repository. Devs: Is this really how it should be working? Should ``fossil export user'' also export the default users? I suppose there is also ``fossil config merge fossil.users'' which won't wipe them out, but it certainly was a bit unexpected to lose all those users (thankfully a test repo). Andy -- TAI64 timestamp: 400000005482744d _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
