Remote repository with bazaar

[John Arbash Meinel]

(Don't forget to Reply All, so that others can participate in the
discussion).

Massimo Manca wrote:
> John Arbash Meinel ha scritto:
>> Massimo Manca wrote:

...

> The main reason is that I need a repository that could be always on line
> and always accessible, I have an hosted web server (also with a cgi-bin
> directory but with some limits) with unlimited disk space and so I think
> it is a good solution to have a bazaar repository on it. I suppose that
> the main problem is if 2 developers try to write at the same time on the
> remote repository, is the result predictable? I am not sure. I am still
> new to bazzar so I need to study a lot, is it possible to have a bazaar
> server on a hosted web space? I may write on my personal cgi-bin
> directory may be sufficient to run the bazaar server?

If all you need is a "always on-line and accessible" repository, then
you already have everything you need. 'bzr push ftp://host/path/on/host'
will do what you want.

If you create a lot of branches of the same project, you may want to
"bzr init-repo --no-trees ftp://host/path/to/repo" before you do:

"bzr push ftp://host/path/to/repo/branch1".

so that when you do "bzr push ftp://host/path/to/repo/branch2" it
doesn't have to copy any data that 'branch1' already has.


We use locking (that should work even through ftp), so if 2 developers
push at the same time, one of them will get a "this is locked" message,
and bzr will wait up to 5 minutes for the lock to be released before
canceling the request.


You don't need to install the bazaar server. It may be a bit faster than
plain ftp (especially in a release or two). I don't know what access you
have in cgi-bin. But running bzr requires having python2.4 available.

John
=:->