On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou <to...@acm.org> wrote: > I have several repos open at the same time, not always the same ones. Before > I swap computers (home <=> work) I would like to close all open repos on one > site, and take a backup to take to the other site.
I wanted to add my two cents here because this is very similar to my current workflow. I'm currently in a Windows environment and don't have access to a server. Though I use fossil, I basically only use it in one repository. I have `c:\spw\fossils\projectname.fossil` that holds the main repository. Then I have a checkout in `c:\spw\code` I work in code, then `fossil commit` to "send" my changes to fossils. Problem, obviously, is that if this drive fails I'm totally hosed. So what I do is copy the repo from fossils to H:\ for backup purposes. H:\ is a network drive that contains my "home" folder on Windows. Periodically I use the "copy" command to copy the fossils repo over to H:\. This seems "fine" although I always get nervous I'll accidentally switch the arguments around or somehow otherwise delete the main repo. I would really like the option to autosync to another directory rather than a remote system. However, based on the sync documentation on the fossil web site, it seems since sync is HTTP based, so HTTP'ing to another dir is probably not an option. I suppose I could `fossil ui` or `fossil serve` from a checkout in the other repository and use sync that way, but there are lots of steps there. Also I saw in another thread the presence of a "file://" URL scheme, but saw no mention of it in the sync documentation. If it does exist perhaps it's a solution for me. Is this related to what Tony P. is saying or am I completely in left field? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
