Thus said Charles Curtit on Fri, 15 Aug 2014 20:37:25 -0000: > One question stick up in my mind. Can a server handle fsyncs from > multiple peers at the same time ?
If by fsyncs you mean fossil sync operations then the answer is yes. > Satellite offices have tens or hundreds of users, but very few > contributors. Triggering fsync upon each repo modification might just > be viable. You would have to figure out how to trigger a fossil sync operation from the satellite to the central after a change is detected. One way (as other have suggested) is to have a cronjob that monitors the fossil for changes and then does a sync when necessary. If cron is not real-time enough for you, then you could use inotifywait on Linux (fnotify[1] if you're on BSD) to monitor the fossil repository on the satellite. inotifywait would then kick off a script that checks to see if the change is worthy of synchronizing to the central office and if true, then it runs a fossil sync (perhaps combined with setlock to prevent multiple syncs from running in parallel). Then you could still have a cronjob that runs the same script once every 5 minutes or whatever is appropriate just to be safe. [1]. https://github.com/Ishpeck/fnotify > Is it also possible to have branches on the wiki ? If you use the embedded documentation, yes, though there is no interface for editing them (except your favorite local editor). > How are user accounts managed ? per server I'd imagine ? Can you walk > me thru what happens once a user has been created on a server, the > next time fsync is run ? How do user rights tie into this ? You can synchronize users between the central server and the satellites, or you can keep their user databases independent. It depends on how you want to manage it. While normally users are local information, you can use the configuration subcommand to synchronize users between sites: http://www.fossil-scm.org/fossil/help/config For example, on each satellite you could periodically run: fossil configuration pull user To sync user databases requires the Admin capability. Andy -- TAI64 timestamp: 4000000053efbf3b _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
