On Wed, Aug 14, 2013 at 07:56:52PM +0100, [email protected] wrote: > > Then, looking at help for configuration it seems as though a Push version > is available: > > fossil configuration push AREA ?URL? > > Push the local configuration into the remote server identified > by URL. Admin privilege is required on the remote server for > this to work. When the same record exists both locally and on > the remote end, the one that was most recently changed wins. > Use the --legacy flag when talking to holder servers.
This, unfortunately, will not work for my needs, because of the requirement for admin privileges for developers to change their passwords. Without some way for them to set their own passwords, I basically have to set their passwords for them -- which means their passwords will not be private. Even worse, it means that for those who do not (for whatever reason) have email encryption set up, emailing a password for me so I can set it would mean sending it in cleartext. Is there another option for this when developers basically do not have access to the server where the main Fossil repo is located except by way of clone/pull/push/sync? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
