"Have you tried self-hosting?" is the new

"Have you tried turning it off and on again?"

🙄

Reply to this note

Please Login to reply.

Discussion

Self-hosting does not fix bugs, make anything easier to use, or necessarily even improve performance.

I've got servers and code bases up the whazoo, lately, and shit still don't work.

I got my own crap to program. I can't go around fixing everyone else's crap.

You know why you don't realize this?

You self-host stuff you barely use, yourself, and that nobody else uses. You're not self-hosting something used by entire groups of people.

I self-host email server to be able to manage it actually, I can't trust a 3rd party with it

I loved self-hosting my email server but at&t, and their shenanigans, made it a nightmare to maintain. I recently moved to purelymail.com real easy to setup and very affordable. Would recommend 🫡

What shenanigans are yoy talking about? If you are referring to their spam filtering, they are pretty responsive at their abuse_rbl email.

And like 40 of you will fork or download a code base and tweak it, slightly, so that it actually works, but never submit a PR. 🥴

Docker based setups should be a bit easier to replicate?

"My system is so well-designed that you need docker, for it to work."

-- No competent engineer, ever.

You probably mean "you need docker to self host it".

The only way to guarantee consistent behavior of software across different devices is if they all share the same base environment. If this can be achieved by any other means great.

It is one of the solutions to "it works on my computer problem". Most home server solutions (start9,umbrel etc) are built around this.

Doesn't matter if it is well designed if it can only run on the Creator's system.

I see the point you're making, but I'd argue it's pretty BS irl. I build pretty large polyglot (C, C++, C#, TS) server applications that are designed to be deployed on bare metal with minimal setup. The complexity is not there, and even C applications, which generally don't have build tools or package managers like most other languages, still isn't all that complex to deploy IMO.

Honestly I think that's starting to become most projects now. The only reason node project's are usually supported outside of containers is because it's all monoglot. npm run x. That and fucking environment variables for configuration. It really bothers me.

From my Simple-Bookmark app readme

"Simple-bookmark was built bare-metal as the primary target, this is because I believe users should have the support to deploy open source apps easily outside of a container. So while a container deployment is an option, the container is actually built from the Linux-x64 package during CI build time."

"I can't get this to work."

"Have you tried self-hosting?"

"Yes."

"Oh. Okay. Have you tried turning it off and on again?"

Y'all's plan for perfectly functioning software.