Self-hosting is the opposite of using a 3rd party cloud service like Dropbox or Google Drive, and instead to host an equivalent service, like Nextcloud, on their own hardware. For every popular cloud service there is probably an independently developed open source equivalent one can host on their own hardware. Self-hosting gives one control, and peace of mind that their private information is not being sold to others, and it can save a lot of money from service fees that aren't paid. The personal security implications are huge, since it is known that governments around the world are pressuring internet services for data on user activity. While there is a legitimate need to know about criminal activities, do we really need to risk our data being snooped upon?
(September 27, 2020) Self-hosting is about hosting Internet services on your computers, controlled by you. This is different from just to just Use the Cloud by signing up for services like Dropbox, Github, Travis, or other 3rd party controlled services. Many people just use the cloud that way, because it's easy to just sign up, provide a credit card number, and get on with business. For each of those commercial services there are equivalent open source alternatives you can host on your own hardware. Self-hosting purposely takes a different route, and in this article we'll go over some reasons why.
(March 15, 2020) When developing Docker images it's useful to store them in a Docker registry. While using Docker Hub is free, it's bad form to fill up that shared resource with images built for personal use. It's better to only publish the Docker images that are truly useful to everyone, and that have documentation. That leaves us with the problem of a location to host our own Docker images. Do we pay for a private repository somewhere? Or, as a self-hoster, do we host a local Docker Registry to store our personal Docker images? In this post let's explore the latter idea.