On Tue, Feb 12, 2013 at 4:17 PM, Jonathan Otsuka <djg...@gmail.com> wrote:
> Is the best way to keep things in sync is to use a schedule task/cron to > run fossil sync? > That's what I do, to keep the various Fossil self-hosting repositories in sync. The primary repo is at http://www.fossil-scm.org/ (Dallas). Clones are at http://www2.fossil-scm.org/ (New York) and http://www3.fossil-scm.org/(Fremont). The crontab on http://www3.fossil-scm.org/ looks like this: # Sync fossil at 43 minutes after the hour every 3rd hour 43 1-23/3 * * * $HOME/bin/sync_fossil >> $HOME/sync.out 2>&1 $HOME/bin/sync_fossil is a simple shell script that invokes "fossil sync" on several different repos. There is a similar crontab at http://www2.fossil-scm.org/ If you are talking about syncing your desktop to a server, in that case I normally just run: fossil all sync periodically from my desktop (like every morning) to make sure everything is synced up. It is also useful to run fossil all changes every evening to make sure I haven't forgotten to do a commit on one or more of the 30-odd repos that I work with on a regular basis. > > Jonathan Otsuka > > On Jan 29, 2013, at 5:01 PM, djg...@gmail.com wrote: > > > I cloned a remote fossil with: > > fossil clone http://user:pass@website wiki.fossil > > > > open wiki.fossil: > > fossil open wiki.fossil > > > > then setup remote-url with: > > fossil remote-url http://website > > > > But then after making changes on either wiki changes are auto synced. Is > this even possible? I can manually run fossil sync and will push/pull > changes. > > > > Jonathan Otsuka > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
