Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Okay here is the situation, I bought a hosting server that gives me version control and ssh access. I'm working on a big project that needs team work so I need at least 10 person around the globe to work on the project,.

this is the structure of the project:

/home/site1
/home/site2
/home/site3

3 of those 10 person work on site1, other 3 on site2, and other 4 work on site3. And the first 3 person who work on site1 should NOT be able to access to site2 and site3 and so on.

I have only one username on my server which is the one my hosting gave me which i have to give it to my team workers.

Any suggestions?

share|improve this question

migrated from stackoverflow.com Jun 29 '10 at 10:02

This question came from our site for professional and enthusiast programmers.

2  
This is possible with SVN, but as you are not giving any details about what kind of access to have to configure it, it's impossible to say how. –  Pekka 웃 Jun 29 '10 at 9:55
    
I can remember, with visualSVN on windows I could make users to authenticate to the server before they could commit! How can I achieve that with SVN> –  user24912 Jun 29 '10 at 9:58

4 Answers 4

Indeed details would be useful. SVN can be easily partitioned into seperate repositories, each with their own set of users and permissions. Apache + mod_svn (with SSL of course enabled) is an easy to configure / use system but if ssh is actually needed details of use are as well.

share|improve this answer
    
it seems like you could probably find a hosting server solution that has SVN already setup on it such as this: a2hosting.com/web-development/svn-subversion-hosting –  djangofan Jun 29 '10 at 16:22

If you use git, gitolite can work from a single account and preserve your existing authorized_keys entries. Still, be careful you don't lock yourself out.

share|improve this answer

Indefero is effectively a GoogleCode clone. If you do not need SVN per se it is a nice option for your situation, giving you a complete (private) system to work with. And in my experience git is easier to setup than SVN.

share|improve this answer

You don't trust them for access to your SVN repository, but you do trust the code that they will write? I believe you're trying to protect the wrong aspect of your project.

In any case, SVN works over dav, and you can put username authentication on it through apache and they wouldn't even require a shell account to the machine. You can also use PAM to do your auth in which case you could just restrict their access with /bin/false and just let SVN do the authentication.

share|improve this answer
    
The OP won't be getting permission to configure PAM on a shared host. –  Tobu Jun 29 '10 at 16:23
    
Then it is a non issue, SVN can authenticate from .htpasswd rather than requiring PAM authentication. Since it is SSL, the password isn't passed in the clear and it doesn't require actual user accounts on the machine. –  karmawhore Jun 29 '10 at 16:53

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.