Is this (centralized) Workflow something i should/could use Bazaar for?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sebastian Paul wrote:
> I'm kind of an admin for a small Webdesign Startup.
> 
> We'd like to develop html themes for drupal on a central server, and
> push changes in revision control.
> Branching and developing locally is a bit of a problem because we would
> need to use the central mysql database which we can't check out and in
> to work with it locally.
> Actually most of the devs at the moment develop by simply using ftp over
> gvfs.
> 
> I was trying to mount the server directory with sshfs to my local
> machine and then use local bazaar to do the revision control.
> But that was too slow to be usable.
> 
> One solution would be to give the web developers shell access to the
> server and use the bazaar instance installed there, but the devs are not
> used to working with cli and i would like to give them a GUI ( Qbzr).
> So what i would need is some sort of web interface that would trigger
> bazaar on the server to first of all commit, and perhaps show logs (but
> that could also be done with loggerhead).
> 
> Or to provide kind of a hook to qbzr to get the changes that are
> generated by bzr on the server.
> 
> Is there someone using that kind of workflow?

I'm not sure I understand everything, but if you could use a checkout
(bzr checkout bzr+ssh://server/location)

At that point, when you do 'bzr commit' locally, it will update the
*branch* of the server. (If you are out of date, then you have to 'bzr
update' before you can commit.)

It doesn't, by default, update the *working tree* of the server. There
is the "lp:bzr-push-and-update" plugin which will do this for you. (at
commit/push time, it checks to see if there is a remote working tree,
and runs 'ssh host bzr update /location' for you.)

Each user would need to have this installed (as
~/.bazaar/plugins/push_and_update).

Another alternative would be a cron job on the server, which just runs
"bzr update" periodically, that would introduce a bit of lag from the
time they run "bzr commit" to the time it shows up, but doesn't require
a plugin.

There are other options, but this is probably the easiest. At that
point, they develop locally, and can view everything from their local
machine, but then when they "bzr commit" it would then be sent to the
server. (Or commit via qbzr, etc.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknLphMACgkQJdeBCYSNAANL0QCbBKdR49q2ZiVESLUHfOzozd6Q
Z8QAnjhqYXLs00AWY582DgoipLlTTVvd
=3uyJ
-----END PGP SIGNATURE-----