Version Control (GIT) shared access??

[MuGeN]

Ok, so I've installed git, and i understand how to clone a copy of the project and checkout new branches etc etc (all through the terminal on my mac - haven't looked at GUIs yet...)

What I want to know is a fundamental thing that I'm unsure of, and that is how to collaborate with this system...

is it as simple as giving people access to a certain folder on my computer via SSH or something? I've got to admit file sharing is not a strong point of mine I've never managed to reliably set up sharing across a network (between macs and pcs) never mind over the tinterweb...

is it a case of doing port forwarding and all that jazz so that someone can get to a folder and then run their $ git whatever commands to pull down copies and all that, or is there a more elegant way of setting it up?

if this is the case, I also don't know the best way to just share one folder on my mac - if i set up a "Sharing Only" user then windows people cant get in, and if I set up a full user on my mac just to get into the repository, then they get access to loads of other stuff too which I don't want...

all in all, could do with a leg up... any advice?

 

[MuGeN]

ho-kay, so i've managed to set things up so i can ssh into my work computer and get around the file system and work with the repository there, so the only fundamental thing which needs properly setting up is how other people should have access, i am obviously logging in with my own details but how would i go about setting up a user which simply has access to one folder on my computer and nothing else? don't even want them to have a home directory to be honest...

could someone help me out?

 

[MuGeN]

Is there any reason you're using GIT? Subversion is much easier to set-up for this. GIT looked painful .

well, i just did a lot of reading over which to go for and the consensus seemed to be that if you are used to svn then stick with it unless the git advantages are particularly suitable for what you are doing, but if starting fresh git seemed to come across as a fresher take on the idea and better in most ways...

do you not agree? git itself doesn't seem hard to get around but i admit the fact that there is more than one repository makes it a bit more complex...

i might have a go with svn since we haven't started the collaboration yet i'm still learning the whole thing, so maybe worth a dabble to make my own mind up...

EDIT: its worth googling "subversion git" - vast majority of sites are taking about "why you should switch to git" or "10 reasons why git is better than subversion" and all that... based on all this stuff i went for git

 

[MuGeN]

I started with subversion and now use git for all new repositories - it's MUCH better for a production environment, in my opinion. Subversion will cry and make things difficult if you try to do anything out of the ordinary (if you accidentally delete a file, you have to update and use svn to remove it otherwise it goes weird) and the linear nature of it makes the "I know you're working on a new version of our site, but can we just make this tiny change?" instances much easier by just being able to branch from a point, make your changes, then merge back into master. Those two things make it head and shoulders above SVN for me.

As Defenestration says, Pro Git is an excellent resource in plain English.

since it sounds like you use git to collaborate on web projects, could you tell me what you do about databases? obviously a db is not something that would be passed around with clones, pushes and pulls?

(btw: thanks for the heads up on Pro Git, read a few chapters and now I've ordered the paper version to support the writer )