TagHosting (Computers)

Github and Distributed Coding

Yarmo writes on his blog:

My interpretation? The Microsoft Github ship is sinking and it’s sinking faster every day. The beauty is: you don’t need them.


I agree, you don’t need Github. In fact, you don’t need much of an infrastructure at all. That all being said, I don’t think Github is sinking per-se. Microsoft hasn’t even owned them for that long, and their recent purchase and integration of Node/NPM into the system ensures that they’re going to stick around for a bit.

I do, however, agree that hosting your code is something you can easily do on a wide variety of systems. I, personally, use Github. I do have all of my repositories backed up to my NAS, just in case. I’ve used Gitlab, and while they’re very good, I don’t need 80% of the features (same with Github). I used to have a self-hosted Gitea instance, but managing my own stuff became too much of a burden, especially on my anemic Raspberry Pi 3 (1gb).

Thankfully, there are a lot of hosts out there, as Yarmo points out:

selfhost your own Gitea instance if you have the knowledge;

use Codeberg.org which also uses Gitea;

use sourcehut.org which takes a different but very solid approach to git hosting;

use any instance generously hosted by amazing people (think libreho.st and Chatons);

use gitlab.com or selfhost an instance.


Git, being distributed in nature, allows you to host in all of those places, all at once. Pick and choose or just use one. Depends on what your personal needs are.

Github isn’t going away, it’s just getting the same kind of Microsoft hosted services administration that we’re seeing in Office 365: Lots of little blackouts and brownouts.


So, I have a bad habit: I break things. Usually things that I’m tinkering with, either to understand better, to “optimize”, or to just find out how the damn thing actually works. My website is a prime example of this behavior. I broke it recently, and instead of just restoring it like magic, I moved it to the NameCheap shared hosting instead of their (quixotically) more expensive managed hosting.

I also host a number of different applications on this hosting, so it ends up being a better deal. I’ll do my best to import some latent desired posts, like Garrett’s quotes, but that’ll come in time. Right now, I’m just shifting stuff around and making sure things are more suited to my desires. So far, so good.

Goods and Services

In a previous post, I talked about using Feedbin and Pocket as tools to help me stem the flow of information overload. These then allowed me to take breaks in which I could sift through the information and save what I cared about for later reading. This actually ended up being really effective for me. The biggest problem was I was paying, effectively, $10 a month for the news.

Initially, I didn’t have a problem with this. My feeds and saved articles were available everywhere. I could save from one to the other and move on with my day. Something was still nagging at me, though. I am not a heavy user of either service. I don’t have hundreds of feeds to process, nor do I save hundreds of articles to read for later. I also am knowledgeable enough to be able to set these services up on my own. I just didn’t have a platform in which to do that. Until yesterday.

It turns out, when you’re too close to a problem, you miss the obvious. In this case, I realized I could use shared hosting on pretty much any platform to, effectively, “self host”. While not the most ideal setup, it would suffice, and it would be massively cheaper that what I was doing now. So, that’s what I did. I purchased the cheapest hosting plan from Namecheap, wired up some DNS entries and pointed them at the subdomains I’d setup for the different tools. Now I was hosting TT-RSS and Wallabag on my own for less than $2 a month. I have much the same workflow (though, a little more messy), but I’m not paying through the nose for something I use maybe once or twice a day.


I moved away from using Jekyll for a couple of reasons:

  1. The massive amount of required modules (both Node.js modules and Ruby Gems) to do basic stuff
    • Almost 300 in total
    • Many of these were out of date and had security issues or dependency issues
  2. I couldn’t update my site on-the-go
  3. Lots of small things required architectural changes

That all being said, I still love the idea of static site generators, but I feel they’re not worth the effort for me. I’m lazy and my life is getting busier. I want convenience.

Therefore, I moved into NameCheap’s managed WordPress hosting EasyWP. Since it’s all connected inside my registrar, it’s easy to just plug in and go. Honestly, it doesn’t even feel like a managed install, either. I get pretty much the full experience using WordPress without all the overhead of managing, securing and otherwise babysitting PHP, Nginx, MySQL (MariaDB), and the whole stack underneath.

If you’d like to give it a try, or were looking for a way to get a free month, you can use my referral link: https://dashboard.easywp.com/r/pwq8d

© 2020 Verily

Theme by Anders NorénUp ↑