On Fri, Aug 1, 2014 at 9:02 AM, David Botham <[email protected]> wrote:
> All, > > I am in the process of moving from git to fossil. > > My question is about how many repositories to use for a particular project. > > A summary of my use case: > > - Single developer, but, may from time to time (once a year) have someone > else I work with want to contribute. And those contribs are usually small. > - I alter the code for my projects on different computers (workstation at > the office, laptop on the road, etc...). > - I use DropBox as a data store. > - Mostly I develop on Windows, but, target Windows and Linux (and now and > then OSX). > I don't know how closely a DropBox folder follows correct (published) filesystem semantics. If DropBox is doing some no-standard things, then it might be possible to corrupt the repository if it lives in a DropBox folder. I just don't know. I'd be inclined to keep the master repos in an ordinary folder on your desktop. Run a Fossil server on that desktop that grants access to your laptop and/or other systems. In other words, the laptop clones from the desktop. If you run "fossil remote" on the laptop it will show the URL of the desktop Fossil server. Suppose your normally work on your desktop. Before changing to another machine, simply run "fossil all changes" to make sure you have checked in everything that you want to have checked in. Then if you are taking your laptop off-network, go to the laptop and type "fossil sync all". That will completely sync all your repos. After making changes on the laptop while off-network, just type "fossil all sync" again and all your changes will go back to the desktop. The above is how Fossil is *designed* to work. Can you get it to also work using your DropBox approach? Maybe. It will require some experimentation, I suppose, to determine whether or not DropBox is pulling any dirty tricks that get the underlying SQLite storage engine confused. Perhaps others on this list can give a better answer. Rather than putting the master repos on your desktop, you could lease a Linux VM on the open internet for $10 or $20/month, and host all of your repositories there. Then you'd also have a machine on which to put shared files and a website and an FTP server and you would have a remote backup of all of your work. > > After reading the docs and Jim's book, I setup like this: > + Main repo on DropBox: > c:\> cd DropBox\fossil-repos > c:\DropBox\fossil-repos\> fossil new my-project.fossil > > + Clone the repo in DropBox to my local workstation, laptop, etc, so on > each, I do this: > c:\> cd fossil-repo-clones > c:\fossil-repo-clones\> fossil clone > \DropBox\fossil-repos\my-project.fossil my-project.fossil > > + Open the local clone in a dedicated development directory and commit the > initial files (intial file commit done once, on the system where the code > base starts): > c:\> cd dev-projects\my-project > c:\dev-projects\my-project\> fossil open > \fossil-repo-clones\my-project.fossil > c:\dev-projects\my-project\> fossil add . > <output here...> > c:\dev-projects\my-project\> fossil commit -m "Initial commit of files. > Starting development." > > > My big question is, am I wasting my time creating the local clones on all > my different systems? Should I just the repo in my DropBox and simply open > on my various systems? > > > > Thanks in advance for looking at my issue and helping. > > > David > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
