gitHub or TortoiseSVN

Pho3nix

Pho3nix

The Legend
Joined
Jul 31, 2009
Messages
32,827
Reaction score
3,033
Location
On the toilet
Hi all,

Our TFS server is having issues at the moment and managing versions of code is becoming a big problem.
Need something wherein when I close my laptop I can work from home after pushing the changes up onto the server.

Can any of guys recommend something I might be missing here?
Online storage is preferred and open source aswell :).
 
I personally love Subversion, and prefer it to git because it is more secure. Also, the private repositories on git are quite expensive, and I'm not happy storing code online. Rather have it behind our firewalls and check in from the outside.
 
except at bitbucket where where they're free. also have no clue what you're on about regarding security. how is subversion more secure? gits awesome if you branch a lot and want to occasionally try something out on the codebase without annoying everyone else. local branching is something svn can't do
 
Last edited:
We use assembla at work, and i use github at home.
 
also having code behind a firewall that you check in from outside is exactly what online code is. only i trust people who hold facebooks code and google's code a lot more when it comes to setting up the firewall than i trust timmy from downstairs.
 
Subversion is a centralised source control system where the repository is stored on a single server, and Git is a decentralised source control system where every user has got a copy of the whole repository stored on their computer.
 
How do management feel about your plan to move the company's source code - i.e. the company's IP - off-site / into the cloud ?

You could get yourself into a world of hurt if you do so without their express permission.

I would suggest that - whichever SCM you use - you keep it in-house and either re-synch each morning (when you get to work) or via a VPN.
 
rrh said:
How do management feel about your plan to move the company's source code - i.e. the company's IP - off-site / into the cloud ?

You could get yourself into a world of hurt if you do so without their express permission.

I would suggest that - whichever SCM you use - you keep it in-house and either re-synch each morning (when you get to work) or via a VPN.
Click to expand...

In-different at the moment. Was told to get it done ASAP and with source safe and VPN being on the fritz this was a possible fix.
Appreciate you bringing this up and I'll mention if again so we get a concise answer.
 
Pho3nix said:
In-different at the moment. Was told to get it done ASAP and with source safe and VPN being on the fritz this was a possible fix.
Appreciate you bringing this up and I'll mention if again so we get a concise answer.
Click to expand...

In writing would be good :)

BTW after TFS you may find Subversion - with TortoiseSVN & the Ankh plug-in for VS - an easier move.

Anything other than VSS !
 
git on bitbucket definitely

subversion is ****. ok, it's not really.

but if you do any sort of branching and merging, git is far superior
 
Having used both extensively, I thing git is far superior to SVN.

Also, if you are going to host offsite, I think using github or similar is a much better option that hosting your own server somewhere. With your own server, managing and backing up the server becomes your problem.
 
You still need a centralised server with Git if you want to sync everyone's changes together.
 
Obviously, that's what bitbucket/github is for ;)
 
Last edited:
The first company i worked at had the source control on some old box, i told them that we needed to get a new server incase of failure. They argued with me said its not in the budget, the lead developer at the time said it was not necessary.

A week later the hard drive crashed in that server. Thankfully we had the repositories backed up to our local drives, but it just go's to show that these things can go at anytime.
 
semaphore said:
The first company i worked at had the source control on some old box, i told them that we needed to get a new server incase of failure. They argued with me said its not in the budget, the lead developer at the time said it was not necessary.

A week later the hard drive crashed in that server. Thankfully we had the repositories backed up to our local drives, but it just go's to show that these things can go at anytime.
Click to expand...

With Git this wouldn't be a problem cos everyone has a copy of the whole repository. With Subversion this would have been a major stuff up cos only the server would have had the whole repository.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X