391–400 of 625 posts
I was thinking about self hosting my podcast [1], but it's an insane amount of effort and will cost money. Compared to using anchor for free, that's owned by Spotify.
For starters, I'd need to figure out RSS, figure out how to distribute the podcast and how to store it (+ costs). Not impossible sure, but not ideal either.
[1] The Language of My Soul Podcast https://anchor.fm/lang-of-my-soul
Disclosure - the founder of LibHunt.
With regards to self-hosting, https://selfhosted.libhunt.com/ could be helpful. Disclosure - the founder of LibHunt.
Earlier quoted context omitted.
There are numerous projects which have attempted to create this. https://sandstorm.io/ was the biggest one but as far as I can tell its largely unmaintained and most of the apps are outdated https://yunohost.org/ probably has the best "just works" experience but I didn't like that it wasn't using any kind of containerization which has caused them issues with shared libraries like PHP being difficult to update. As wel…
I always check for yunohost on these self-hosting threads. Standing up a yunohost on my raspberry pie has been on my to-do list for a long time. Unfortunately their default for my raspberry pie didn't "just work" on the Saturday evening I tried it. It was my first foray with that raspberry pie, so installed a different server OS and spent the rest of the evening setting up a basic server for an HTML file and learning…
These 1 click install services like yuno host achieve it through huge amounts of work per app and patches over upstream.
Problem is its a monster of a job that requires upstream projects to be onboard and ultimately most of these tools are meant for enterprises to run who just have a dedicated ops person so complexity and maintenance are less of an issue.
Earlier quoted context omitted.
>For a technologist or engineer, yes. For a layperson, no. The average consumer who desires privacy is probably neither a technologist or engineer, so the longterm target is something that just works. In comparison to system V initd startup files, systemd unit files are, arguably, less complicated. I'd say the "complexity" of systemd unit files is mostly irrelevant to end users. For a relatively non-technical user, i…
I'd go a step further: programs aimed to make self-hosting easy should not even need a package manager. They should be self contained (statically linked) binaries. Luckily we have Go which makes this very easy to achieve, and to make things better, Go is designed for web servers. I believe we've had this ability for almost a decade, and still no one is harnessing it to make self-hosting easy and reliable. Further mor…
It would have been much harder to pull this off if these services required large interpreters, adjacent daemons running, and complex orchestration. Given the amount of time I have, I might have just skipped the SELinux step.
Earlier quoted context omitted.
This is where docker really shines. Unless you’re a php developer or have a lot of experience with it, gluing it all together is best left to some clever person maintaining an upstream docker image.
Docker and I are not friends. The quickest way I found to fill up my limited VPS hard drive was to install Docker. All the work arounds to limit it failed. Then there's the whole lack of concrete control over iptables, where a tiny mistake can open you up to all sorts of horrors. So, it's great that Docker works for many, but I get the exact opposite of warm and fuzzy for it however.
Earlier quoted context omitted.
> SystemD is complicated for a layperson Is it? It has clean and logical abstractions, and consistency. Services depending in each other isn‘t complex or difficult to understand. I suspect that a nice GUI would make systemd quite usable for non-expert users. BTW: It‘s called ”systemd“: > Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. [0] [0]: https://www.freedeskt…
Comments like yours are a great example of why Linux has a hard time being user friendly. You take something that's deeply technical but easy to understand for yourself, and somehow generalize it to everyone. "If it's easy for me, it is easy for everyone", without noticing that perhaps your expertise plays a big role in making it easy. The better question is why should a layperson ever need to know about systemd in t…
> A system where editing text files can make or break the system, is not a reliable system. It's easy to make mistakes in text files. Specially for users without expertise.
I don’t think that’s a salvageable notion of “reliability”. I could bork Mac OS or Windows easily enough by editing text files, if I really wanted to.
Earlier quoted context omitted.
But readers might
I'm okay with forcing people to choose between anonymity and reading my content. I'm not going to publish anything that they have any reason to hide, with very high probability.