El 1 feb. 2017 9:55, "Luca Ferrari" <fluca1...@infinito.it> escribió:
On Tue, Jan 31, 2017 at 12:25 AM, Martin Irvine <martin_irv...@bigpond.com.au> wrote: > “Temporarily” means I will usually not want to leave a > copy of the source code or the repository on the PC when I am finished Sorry, but this sounds not good to me. Either you don't trust your clients or you are carrying on any kind of secret, but this could not be a solution. Instead of using only a flash drive as "main storage", consider leaving a copy on the pc(s) but encrypt it. This way you could gain: backups (all pcs will have a more or less sync version), reliability (at least, much more with respect to flash drives), and can forgot the copy in-out workflow just leaving fossil to do the "sync" for you. Luca Hi, I agree with Luca and what others already have mentioned; avoid copying files, as that undermines the whole idea of the usage of a repository; use checkout and commit instead If you want to use your Flash drive as a central point, store the fossil binary and your repos there, and checkout the source code to your client's PC. When your are done on that PC, commit your changes to the repos, and you may then delete/encrypt the working copy of the source code. As others also have mentioned, you should really think of having a backup system, using a remote server for your repos. (A shared web hosting account is a few US dollars a month.) You can configure fossil to turn off autosync, to commit to your Flash repos, but to avoid the commit to trying it all the way to the remote server. When you are connected to Internet, you should push your commit(s) to the remote server. See fossil help remote-url to get an idea how to configure the repos on your Flash drive to point to the remote server. Best Regards, Johan
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
