[fossil-users] Open a remote repository?

[Christopher Berardi]

Is it possible to open a fossil repository that isn't cloned locally?
For example, suppose I have a fossil repository stored on a remote
server -- can I forgo cloning it and do a straight open, such as:

$ fossil open http://dev.mysite.com/myrepo.fossil

The benefit of this is that it enforces the client-server and 'one true
canonical source' paradigms in the strictest possible sense (as far as I
can tell) and I would think that it could limit the amount of data
needed to get started on very large/long running projects. The obvious
downside is that any benefits gained from the dvcs paradigm is
more-or-less nullified.

--
Christopher Berardi
http://www.natoufa.com/

May grace and peace by yours in abundance.
_______________________________________________
fossil-users mailing list
fossil...@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Benoit Mortgat]

On Mon, Mar 19, 2012 at 11:28, Christopher Berardi <cber...@natoufa.com> wrote:
> Is it possible to open a fossil repository that isn't cloned locally?
> For example, suppose I have a fossil repository stored on a remote
> server -- can I forgo cloning it and do a straight open, such as:
>
>    $ fossil open http://dev.mysite.com/myrepo.fossil

No, this is not possible. Note that when you clone, you create some
vassality relationship between your cloned repository and the original
(the auto-sync URL is automatically set). So, whenever you try to
update, commit, pull is automatically done before, and push after commit
if you have the rights.

With your method it would be difficult to commit or perform many
operations: fossil needs direct access to the repository as it performs
SQL operations on it. If you want a single, central repository, then
why don't you use fuse (Linux) or mount a network unit (Windows) to have
access to the repository as if it was on your file system?

--
Benoit Mortgat