On Mon, Nov 1, 2010 at 11:46 AM, Laurens Van Houtven <[email protected]>wrote:
> Hi. > > > Let's say I have a development shop with a few developers and a similar > workflow (ticket states etc). Is there a recommended way of keeping this > configuration (including users if at all possible) in sync between multiple > Fossil repos? Can I just copy over the relevant tables and expect everything > to Just Work? > If the user passwords are cleartext, then you can just copy the "user" table from one repository to another. But if users change their passwords using the UI, then the passwords are stored as an SHA1 hash. And the SHA1 hash is seeded by the repository ID, which means that copying the "user" table from one repository to another won't work. This is by design: It allows a user to specify the same password on multiple repositories, without that being obvious to someone who can only see the hashes. If your web server can be configured to do its own login credential checking and then set the REMOTE_USER environment variable to the name of the logged in user, then that will server to give everybody a common login. > > thanks > lvh > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
