On Mon, Apr 30, 2012 at 8:17 AM, Leo Razoumov <slonik...@gmail.com> wrote:
> On Sat, Apr 28, 2012 at 09:34, Richard Hipp <d...@sqlite.org> wrote: > > > > On a server, I often have multiple CGI scripts all pointing to the same > > repository. A similar feature, added at the same time, keeps track of > all > > of the possible URLs for accessing a repository. On the main Fossil > > webserver for example, I just now did "fossil info fossil.fossil" and I > see > > this: > > > > access-url: http://fossil-scm.hwaci.com/fossil > > 2012-04-28 > > .... > > I think this means that every time one accesses a repository via > cg-bin the repository updates the "baseurl:..." entry. This would make > rsync based replication/backup scripts go nuts (they depend on > timestamps and checksums). > No. The entry is only updated if it does not previously exist or if the database file was changing for some other reason. Note that the database already gets updated every time somebody signs in. And Fossil uses the database as a cache in some circumstances, so already many if not most CGI accesses already write to the database file. This has been the case for ages. Note that rsync only transmits the differences between two files, so making small changes to one table is not going to seriously impact rsync performance. The www.fossil-scm.org website is backed up using rsync. And, really, "fossil sync" is a better backup of repositories than "rsync" anyhow. > > Would it be better to have a configuration settings "track-access" > (on/off) and "track-ckout" (on/off) to allow a user to selectively > enable/disable new behavior according to his/her needs? > > --Leo-- > -- 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
