> -----Original Message-----
> From: [email protected] [mailto:fossil-users-
> [email protected]] On Behalf Of Richard Hipp
> Sent: Friday, August 01, 2014 9:15 AM
> To: Fossil SCM user's discussion
> Subject: Re: [fossil-users] (New To Fossil): Repo Workflow / Should I
> Clone Or Use Many Opens
> 
> 
> 
> 
> 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 have been using DropBox for a long time, and don't have any issues / concerns 
from a reliability perspective.  


> 
> 
> 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

It works great, just like a local file, but, automatically synced to all my 
other systems.

Here is a transcript of a commit on my desktop.  Notice that the commit is 
automatically sync'd to both my local clone and up to the primary repo from 
which the clone was taken.
______________________
C:\dev-projects\my-project>fossil status
repository:   \fossil-repo-clones\my-project.fossil
local-root:   C:/dev-projects/my-project/
config-db:    C:/Users/joeuser/AppData/Local/_fossil
checkout:     4af5687de58dac6e94157395a55a1df2a9dd9a7d 2014-07-31 19:55:23 UTC
parent:       40fdf5a098abfc946f12e8287bdd961a705a5e34 2014-07-31 16:02:58 UTC
leaf:         open
tags:         trunk
comment:      [8787849eb4] Updated crud_object() to log object identification
              details for all log level entries. (user: joeuser)
EDITED     my-project.conf

C:\dev-projects\my-project>fossil commit -m "Monir cosmetic updates to conf 
file."
Autosync:  file://N:/Dropbox/fossil-central-repos/my-project.fossil
Round-trips: 1   Artifacts sent: 0  received: 0
Pull finished with 268 bytes sent, 931 bytes received
./my-project.conf contains invalid UTF-8. Use --no-warnings or the 
"encoding-glob" setting to disable this warning.
Commit anyhow (a=all/y/N)? a
New_Version: 53aaeeb16d3ad1766a6923ae8963c7d7316530c9
Autosync:  file://N:/Dropbox/fossil-central-repos/my-project.fossil
Round-trips: 1   Artifacts sent: 2  received: 0
Sync finished with 1232 bytes sent, 980 bytes received
________________________

>From my laptop, the transaction would be pretty much the same.  

So, regardless of where the central repo is located, does it make sense to 
clone it to my workstation / laptop / ect, and then open that, or simply open 
the central repo into my local working directory?


> 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.

I have never had any issues with it, so, I think I am going to trust it.  
Although, if I ever do have issues, I will have to look at another central 
location for the repo.  Although, to clone or not to clone is still the 
question.

> 
> 
> 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.

Thanks for the tip.  I will look into that...

> 
> 
> 
> 
> 
>       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

Reply via email to