Re: [fossil-users] Using Fossil SCM with Master Repositories held on aFlash Drive ?
> So, if everything goes according to plan, I think I could do this > indefinitely without ever needing to push, pull or sync to a Master > Repository ? Is this valid and reasonable, or am I missing something > important here ? Artur Shepilko suggested having Master Repositories on my > Home PC and syncing the repositories on the Flash Drive into these, but (in > a single developer non-networked environment) I do not understand if this > offers any benefit over simply copying the repository files from the Flash > Drive to my Home PC, and knowing that the “backup copies” of my repository > files at home should always be “byte-for-byte identical” to the “live” > versions on my Flash Drive ? > Sounds like you are trying to validate a file-copy approach that you have in mind. Perhaps file-storage instills in you more trust and consistency than Fossil sync. An easy way to advance your choice is to try out the 'fossil sync' route in some test set up, so you could gain more trust in how it operates. It is fairly seamless yet robust. Its design goal is change-consistency, so it off-loads such decisions from the user. I would not consider a Flash drive as main Reference storage, it's a gamble. More of "backup" flash drives -- just a protracted gamble. Flash drive can be a temp workspace or means of transit, that is in the absense of a more reliable transport e.g. network. So I would try to minimize such transit-time, this mitigates the risks for anything that I would care not to accidentally lose. Designating a Reference place/storage in this case would simplify logistics of sync and backup. Be it your "trusted"-PC or someplace online, the field-updates must find their way into it as soon and reliably as possible. Flash-repos then would be considered "repos-in-transit", in general are clones of Reference. There's no practical need to have these repos copied onto a field-PC, since you want to leave it clean afterwards anyway. Also, you would probably do some development on your own PC -- here it is, this needs to sync somehow too. Copying the repo files manually is just another way of sync, just in such case you yourself become the utility that does it. So the success would depend on your discipline about what/where/when/how. Minimizing the need for decisions like that would free up attention and brain-cells for other tasks. For consistency I would rely on "fossil sync" to do the job of keeping those Reference repos up-to-date. Isn't it easier to blame a utility in case it fails, than to assume the blame on self :) Fossil sync protocol is tried and tested, file-copy bypasses it altogether. As for the working copy, Richard's suggestion to use RAM-disk also has a bonus to possibly speed up the builds or anything that does frequent writes; flash writes are annoyingly slow at times, but from experience are quite brisk for commits. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Using Fossil SCM with Master Repositories held on aFlash Drive ?
On 1/30/17, Martin Irvine wrote: > > I am still a bit confused about the pros and cons of cloning > and syncing Fossil repositories vs simply copying the repository files on > and off of the Flash Drive. I don't think you need to mess with clone, push, or pull. Copying files is sufficient. Actually, I think you will be ok to use the *.fossil files directly off of the flash drive. Just do: fossil open d:\repos\project.fossil to check out the files for a project. Then when you are done simply delete the whole folder (after checking in any changes you make). For added security, check out the files to a RAM disk. -- 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
Re: [fossil-users] Using Fossil SCM with Master Repositories held on aFlash Drive ?
Hi Martin, One disadvantage of copying repositories between the thumb drive and your client's PC is that there's a risk of accidentally overwriting a newer repository with an older one. Unlikely, of course, but if it did happen, you'd permanently lose data. Another drawback is that if you have many repositories, you might lose track of which ones have changed and need to be copied back to the thumb drive when you've finished your work. (Or maybe you'd just copy them all). If, as suggested, you have the Master Repositories on the thumb drive, clone them to the client's PC, and check out working copies from the clones, both these problems are solved. "fossil all sync" takes care of everything! I use this model (with a Sync folder instead of a thumb drive), and it works nicely. (Sync is a Dropbox-like service). Ross On Tue, Jan 31, 2017, at 10:25 AM, Martin Irvine wrote: > Hi again, > > A number of people have replied to my questions about using Fossil SCM > with Master Repositories held on a Flash Drive. Thank you all for > your input. I have been experimenting further with Fossil, and have > decided on a plan that I think should work, but I am still am bit > confused about whether or not I should use any Master Repositories, so > I would appreciate any further advice anyone might like to offer on > the following plan. > > But before describing my plan, I would like to clarify a few points to > hopefully avoid any unnecessary discussion about these details: I > understand the long term reliability of Flash Drives is suspect, and > thus it will be important to back-up the files on the Flash Drive > regularly and probably to replace it from time to time. I also > understand moving a Flash Drive from PC to PC raises various virus > related concerns, but I believe I am experienced in managing this. To > implement my plan below, I will of-course keep a copy of Fossil.exe on > the flash drive so it is available at any PC. For the purposes of > this discussion I am a sole developer working only with Windows 7 or > later based PCs. > > My Requirement > I wish to “carry a number of projects around with me” and be able to > temporarily access one or more of these projects at a time on > standalone client-owned PCs. “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 though I may want to take a copy of any changes I > have made to the project with me. “Standalone” means these PCs > usually are not networked to any other PCs and usually do not have any > internet access. > > My Plan > So, my plan is to keep a number of Fossil repository files on a USB > Flash Drive, plug this into the client’s PC and “open” the required > project(s) as needed while I am working at the PC, then optionally > commit any changes back to the repository(s) on the Flash Drive if I > wish to keep them, with appropriate version tracking and comment > recording. > > I am now pretty sure this is all readily do-able using Fossil. But > for my requirements, I am still a bit confused about the pros and cons > of cloning and syncing Fossil repositories vs simply copying the > repository files on and off of the Flash Drive. Given that I am a > single developer and assuming that any work on any project that is to > be retained will only be undertaken by me on one PC at a time, it > seems to me I do not need any Master Repositories (in the sense that > Master Repositories are used to pull, push or sync changes between > independent sources ?) and that I will not need to push, pull or sync > changes anywhere ? Because of this, it seems to me I need only > “ordinary” repositories on the flash drive, which I can open and > commit to “directly”. > > However, as much as possible, I believe in only copying files on-to > and off-of Flash Drives and not using them as “live” media with random > reads, writes and appends occurring to the files they hold. So, in my > intended use of Fossil, when I need to access a project at a client’s > PC I would expect to copy the relevant repository file from my Flash > Drive to the PC’s local hard disk, then open that copy of the > repository onto the local hard disk and work with the source files. > When finished, if I wish to retain any changes I would expect to > commit the changes to the copy of the repository file on the local > hard disk, then copy this updated repository file back onto my Flash > Drive (overwriting the previous version of the repository file) before > deleting the repository and the working files on the local hard disk. > For backup purposes, I would copy the repositories from the Flash > Drive onto my “at home PC” frequently, and from here these copies > would then get included in my home PC backup procedure. When I work > on a project at home I would treat my home PC similarly to a client’s > PC, in that I would open a copy of the project’s repositor
Re: [fossil-users] Using Fossil SCM with Master Repositories held on aFlash Drive ?
Hi again, A number of people have replied to my questions about using Fossil SCM with Master Repositories held on a Flash Drive. Thank you all for your input. I have been experimenting further with Fossil, and have decided on a plan that I think should work, but I am still am bit confused about whether or not I should use any Master Repositories, so I would appreciate any further advice anyone might like to offer on the following plan. But before describing my plan, I would like to clarify a few points to hopefully avoid any unnecessary discussion about these details: I understand the long term reliability of Flash Drives is suspect, and thus it will be important to back-up the files on the Flash Drive regularly and probably to replace it from time to time. I also understand moving a Flash Drive from PC to PC raises various virus related concerns, but I believe I am experienced in managing this. To implement my plan below, I will of-course keep a copy of Fossil.exe on the flash drive so it is available at any PC. For the purposes of this discussion I am a sole developer working only with Windows 7 or later based PCs. My Requirement I wish to "carry a number of projects around with me" and be able to temporarily access one or more of these projects at a time on standalone client-owned PCs. "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 though I may want to take a copy of any changes I have made to the project with me. "Standalone" means these PCs usually are not networked to any other PCs and usually do not have any internet access. My Plan So, my plan is to keep a number of Fossil repository files on a USB Flash Drive, plug this into the client's PC and "open" the required project(s) as needed while I am working at the PC, then optionally commit any changes back to the repository(s) on the Flash Drive if I wish to keep them, with appropriate version tracking and comment recording. I am now pretty sure this is all readily do-able using Fossil. But for my requirements, I am still a bit confused about the pros and cons of cloning and syncing Fossil repositories vs simply copying the repository files on and off of the Flash Drive. Given that I am a single developer and assuming that any work on any project that is to be retained will only be undertaken by me on one PC at a time, it seems to me I do not need any Master Repositories (in the sense that Master Repositories are used to pull, push or sync changes between independent sources ?) and that I will not need to push, pull or sync changes anywhere ? Because of this, it seems to me I need only "ordinary" repositories on the flash drive, which I can open and commit to "directly". However, as much as possible, I believe in only copying files on-to and off-of Flash Drives and not using them as "live" media with random reads, writes and appends occurring to the files they hold. So, in my intended use of Fossil, when I need to access a project at a client's PC I would expect to copy the relevant repository file from my Flash Drive to the PC's local hard disk, then open that copy of the repository onto the local hard disk and work with the source files. When finished, if I wish to retain any changes I would expect to commit the changes to the copy of the repository file on the local hard disk, then copy this updated repository file back onto my Flash Drive (overwriting the previous version of the repository file) before deleting the repository and the working files on the local hard disk. For backup purposes, I would copy the repositories from the Flash Drive onto my "at home PC" frequently, and from here these copies would then get included in my home PC backup procedure. When I work on a project at home I would treat my home PC similarly to a client's PC, in that I would open a copy of the project's repository on my local hard disk, commit changes into this, then copy that repository file onto the Flash Drive. So, if everything goes according to plan, I think I could do this indefinitely without ever needing to push, pull or sync to a Master Repository ? Is this valid and reasonable, or am I missing something important here ? Artur Shepilko suggested having Master Repositories on my Home PC and syncing the repositories on the Flash Drive into these, but (in a single developer non-networked environment) I do not understand if this offers any benefit over simply copying the repository files from the Flash Drive to my Home PC, and knowing that the "backup copies" of my repository files at home should always be "byte-for-byte identical" to the "live" versions on my Flash Drive ? I would appreciate any thoughts, clarification or guidance on this. Thanking you for your assistance, Martin Irvine. - Original Message - From: Martin Irvine To: fossil-users@l
[fossil-users] Download checksums
The download page contains a link to the following page http://www.hwaci.com/fossil_download_checksums.html that contains checksums for some of the files available for download. Unfortunately, those checksums do not cover the current versions listed on the download page. Can the checksum list be updated? Thanks, -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
