Why should we put source code on github?

[Henk]

If you want to keep your source code private you have to pay them 7 dollars per month.

So that is one disadvantage.

[only in it for the money]

[mar]

try bitbucket. you can have as many private repos as you want for free

[xr_a_y]

or simply install gitlab on your own server ...

[AlvaroBegue]

Or simply keep your code open.

[jdart]

I'm quite happy with it. I don't really like the interface of sourceforge/bitbucket, although technically I suppose there is nothing wrong with them.

If you are the only developer and your project is closed-source then the only advantage of putting it on github is having it stored in the cloud (they have reliable redundant storage). But could get the same thing by putting it on Amazon S3, quite cheaply.

--Jon

[smcracraft]

gitlab is great for narrow focus work in small teams if one wants to keep track of one's own code and do the needful.

We use github but I have long advocated for a local server instead, especially now that Microsoft owns github.

[WinPooh]

Another option is to install Dropbox and create your central repo in a synced folder with "git init --bare". No need in a git server at all, just work with a filesystem repo. As a bonus your get incredibly fast pull and push operations on a local machine.

[smcracraft]

Generally, in IT, you want to silo functions on servers or containers (or lambda serverless functions) so that when the given system breaks, it doesn't break everything.

Concentrating everything on one server is a big no-no, even with reliable backup.

Time to restore and get everything back on track and the number of affected services mounts.

Do not put all your eggs in one basket.