Linus? 'That you?

One of the most known programming tool is built on Ruby, Github.

Forgejo contains all of Gitea, and that has the benefit of allowing Forgejo to be a drop-in replacement. With the decision to become a hard fork, this will no longer be guaranteed

I’m glad to see them move their own direction but I’m skeptical considering the amount of commits they take directly from Gitea. I could see this becoming more like a Fedora/Rhel type of fork but we’ll see.

I’m personally staying with Gitea for now as I have yet to find a reason to switch.

I’ve been using hatch lately and being able to setup dependencies, packaging, ruff, and black all in a package.toml and not having to setup virtual environment is really nice. I’d recommend a try.

Whoever thinks suggesting crypto to family members is a good idea deserves the hate.

It’s only a vache if it’s from the Vachier region of France otherwise it’s a sparkling bovine.

If I’m updating the source code already I might as well build my service from it, I really don’t see how building a docker container afterward makes it easier considering the update can also break compatibility with the docker environment.

Also adapting can be a pita when the package is built around a really specific environment. Like if I see that the dockerfile installs a MySQL database can I instead connect it to my PostgreSQL database or is it completely not compatible? That’s not really something the dockerfile would tell me.

I have a love/hate relationship with docker. On one side it’s convenient to have a single line start for your services. On the other side as a self-hoster it made some developers rely only on docker meaning that deploying the stack from source is just an undocumented mess.

Also following the log4j vulnerability I tend to prioritize building from source as some docker package were updated far later than the source code was.

A desktop will give you a world of possible upgrades while not sounding like a constant jet engine. I have a rack at home with a dedicated room and if I wasn’t making money from it I’d downgrade to a tower in a heartbeat.

Servers usually gives you access to a management interface, ecc ram, dual/quad sockets (optional), hot-swap drives, etc. In other words it gives you tools to lower your risk of downtime. It’s usually less of an issue in a homelab so you can save money by staying with consumer grade hardware.

Let me know if you have any specifics you’d like to know about.

Pfsense, home assistant and Jellyfin (depending on how many concurrent watchers and/or transcode) can hit your memory quite hard. If you get all of this running you will basically lock yourself into running this and nothing else.

My rule of thumb is to set a security of 2. If I estimate 16gb of ram peak I’ll go for 32.

As for CPU/PSU, in the same ballpark have you looked at getting something like a laptop? That way you have the integrated UPS and KVM.

In other words, you might not want to trust them because they killed off a Pixel Pass that 25 people signed up for, a Google Podcasts app that was basically a browser in an app shell that was given a proper replacement, a niche business presentation screen in Jamboard, and Stadia…freaking Stadia. They gave you all of your money back and let you keep the controller, guys.

It’s not a good look when right off the bat it dismisses what is valid concerns by treating the opposition like they’re just whining.