R – Favorite server OS and source control system for small project

linuxoperating systemversion control

I am starting a small project with one other developer and need to setup a dedicated system to house our version control and any other short-term needs the project may have. Requirements for the server are:

Free/open source OS.
Must provide source control.
Must run all the time.

That's it. So I know there are about a thousand Linux-based server distros around that can accomplish this, but looking for success stories from anyone who has managed their own server(s) for a small project. Which did you find easiest, most flexible, most powerful, etc?

Side question: favorite source control system and why?

Best Answer

I have a dedicated Ubuntu server using GIT for version control.
Managing private repositories with gitosis. And it's been great.

Manage git repositories, provide access to them over SSH, with tight access control and not needing shell accounts.

gitosis aims to make hosting git repos easier and safer. It manages multiple repositories under one user account, using SSH keys to identify users. End users do not need shell accounts on the server, they will talk to one shared account that will not let them run arbitrary commands.

It's robust, damn fast, and reliable.

Related Solutions

Visual-studio – Should I add the Visual Studio .suo and .user files to source control

These files contain user preference configurations that are in general specific to your machine, so it's better not to put it in SCM. Also, VS will change it almost every time you execute it, so it will always be marked by the SCM as 'changed'. I don't include either, I'm in a project using VS for 2 years and had no problems doing that. The only minor annoyance is that the debug parameters (execution path, deployment target, etc.) are stored in one of those files (don't know which), so if you have a standard for them you won't be able to 'publish' it via SCM for other developers to have the entire development environment 'ready to use'.

Linux – How to change permissions for a folder and its subfolders/files in one step

The other answers are correct, in that chmod -R 755 will set these permissions to all files and subfolders in the tree. But why on earth would you want to? It might make sense for the directories, but why set the execute bit on all the files?

I suspect what you really want to do is set the directories to 755 and either leave the files alone or set them to 644. For this, you can use the find command. For example:

To change all the directories to 755 (drwxr-xr-x):

find /opt/lampp/htdocs -type d -exec chmod 755 {} \;

To change all the files to 644 (-rw-r--r--):

find /opt/lampp/htdocs -type f -exec chmod 644 {} \;

Some splainin': ^{(thanks @tobbez)}

chmod 755 {} specifies the command that will be executed by find for each directory
chmod 644 {} specifies the command that will be executed by find for each file
{} is replaced by the path
; the semicolon tells find that this is the end of the command it's supposed to execute
\; the semicolon is escaped, otherwise it would be interpreted by the shell instead of find

Best Answer

Related Solutions

Visual-studio – Should I add the Visual Studio .suo and .user files to source control

Linux – How to change permissions for a folder and its subfolders/files in one step

Related Topic