Bazaar setup/structure/layout for multiple projects

[Tim Penhey]

On Sat, 16 Apr 2011 02:36:12 Marius Boitor wrote:
> Hi,
> 
> I have a development server(Linux). I only want to use SSH. I will only use
> Bazaar. I need to see what user did what without having to create a user on
> the server for each of the developers.
> 
> The above is my starting point but I would highly appreciate any examples
> on how/what this whole structure can look/be put in place. I'm interested
> in options/examples even for the smallest detail. This must be a long term
> structure.
> 
> Thank you.
> Marius

Hi Marius,

This sounds a lot like what we needed when we created 
Sloecode(https://launchpad.net/sloecode).

Sloecode was developed for a local polytechnic to use for senior year students 
working on their project.

Sloecode uses a simple database to hold user and project information.  Each 
user and project have their own repository.  Users upload their public SSH 
key, and use bzr+ssh to connect to the server.  The sloecode server is a 
twisted python app that doesn't allow shells, and only talks bzr.

On the disk you have two areas:
   user-dir - where the user repositories are kept (these are private to the 
user)
  project-dir - where the project repositories are kepy, these are private to 
the developers for the project.

projects can have observers, who have read-only access, and the admins are 
special.

We are still in the process of packaging this nicely, but it is running live 
now and is in use, so we are pretty confident that it is at least working.

Tim