Centralised server with http push

[Lionel Dricot]

Hello,

I want to create a centralised bzr server that allows pushing and host
different projects. I've followed this guide with success (even if I add to
tweak it a lot) :
http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/http_smart_server.txtAuthentification
is currently not an issue because it intranet only. I will
investigate authentification later (but any pointer on this is already
welcome).

I've several question :

1) In order to work, the bzr smart server directory has to be owned by
www-data. Not a big issue but can we imagine to change that ? (might be with
something like suPhp but for mod_python).

2) Am I right in my usecase ? In order to create a new project, I simply do,
locally :
cd my_folder
bzr init   (how can I do a bzr init in the olive interface ?)
bzr push bzr+http://server/bzr/my_folder


In order to do the equivalent of svn checkout, I do :
bzr branch bzr+http://server/bzr/my_folder
(how can I do a branch in the olive interface ?)

And to do the equivalent of svn commit, I do :
bzr push bzr+http://server/bzr/my_folder

Does it sound right to you ?


3) Something I don't understand : If I follow the bzr init then bzr push
step, the folder on the server will still appear empty ! In fact, every
pushed revision does not appear on the server. But, if I do a bzr branch,
everything is fine. It seems a bit magical and has the side effect that
files are not available over plain http with the apache index. Any solution
?

4) When should I use bzr pull and bzr update ?

5) I always use the same server with a complicate name+path. Is there a way
do make it a shortcut like it was done for launchpad with lp:my_folder ?

6) Authentification (well, it is an issue after all) : how can I know who
commited what ?


Thanks a lot for tips and pointer,

Lionel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20081013/033fd4a7/attachment-0001.htm