[mrmondo]

It's not really that simple. For people that already do it - managing servers is easy and doesn't take much time at all. One of the main reasons to run your own code repo is that you're in control of your data and you're not limited by the performance or features of the upstream vendor. Not to mention how much faster having your code repo running internally is - when you have 100 people commit code to and from git all day along with using other 'cloud' products you end up eating up a lot of bandwidth - and in many countries that's really expensive (Australia being one of them).

Remember companies that sell cloud services have a vested interest in making you believe that it always makes financial sense to use a cloud hosted product which as those of us that have experience in both cloud hosted and on site deployments will tell you is not always the case.

[lelandbatey]

Exactly. I have a somewhat beefy server that I continue to use just for personal things. Once you're well acquainted with self hosting, the successive time investment drops dramatically, and the rewards become substantial.

At this point, my server replaces:

    - A site host
    - Image host
    - Streaming video service (Netflix replacement)
    - File host (Dropbox replacement)
    - Build server
    - Git repository host
    - Proxy
    - Render server
    - Hosts all the random webapps I write
    - Game hosting

By spending my time, I not only get these services, but the expertise to manage and run other services. It's less rewarding in the short term, since I certainly didn't get all this right when I bought the thing, but at this point I am getting a ton of return on my invested time.

[wodenokoto]

Do you need a static ip for that kind of stuff?

[lelandbatey]

It's not necessarily a requirement, but I find it very helpful. Any dedicated server package will include one, so it's not to much of a worry.