> "But if you cannot wait, head over to r/selfhosted"
The irony of this blog post is telling me to visit a non-self hosted cloud service to get started self-hosting.
Start Self Hosting
151–160 of 625 posts
Re: Start Self Hosting
#152Self-hosting is not always the answer for a lot of people. Self-hosting are not easy for laypeople (someone who are not familiar with it) to try to get their feet wet with it. For myself, I am on the level of beginner and I do struggle to stay on self-hosting path. When I set it up, I learn there is more steps that I have to do because the documentations and guides did not bother to explain those step and expect me t…
To do this right you should also think of backups, updates, and monitoring. Self-hosting is true freedom but doing it right for things like email is akin to running a small business. On the positive side docker makes many things a breeze.
I tried with Docker before and it is not a breeze as you think it is. I tried to use Docker for Calibre-Web and it is a pain to make it work. Because Calibre-Web required to access their database in the filesystem outside of Docker. Docker provided minimal (more of lacking) information of how to expose the filesystem for Calibre-Web to use their database. Calibre-Web cannot create their own database, it relies on Calibre, standalone app, to generate the library that it need to have access to. It took me ages to finally to find a way to expose the filesystem and only provide permission to access that particular library.
Re: Start Self Hosting
#153I don’t need a reason why to self host, I need nice, clear, up-to-date tutorials on how to self host various services.
Self hosting should be easy enough for everyday people. Perhaps preconfigured servers that treat services just like apps. Once I have a server setup, I should be able to install (and uninstall) services in a single click. The OS can handle permissions and containers.
Re: Start Self Hosting
#154The post is conflating two separate things as if they are the same. 1) Personal stuff that you created and own. For example photos on Google Photos. If Google decides to remove a random photo from my collection, that would be a big problem for me. But they don't. On the upside, the probability of Google losing my photos is an order of magnitude lower than my personal hard disk failing and me having forgotten to back…
Yes, completely valid to treat it as the same when it's something you want to have access to without any third party denying/removing that access.
That you have no attachments to movies, music or tv shows is just you. Others may want to continue enjoying the media long after it has been removed from online services.
Re: Start Self Hosting
#155I've gone down this path a while back and self-host Gitea and other things: https://taoofmac.com/space/blog/2022/02/12/1930 I will be moving my KVM/LXD setup to Proxmox eventually (probably when I get new hardware) and am looking into low-wattage servers (ARM would be nice, to continue the grand tradition of running services on an NSLU2 a few years back, but there just aren't any good ARM server boards with lots of R…
> I will be moving my KVM/LXD setup to Proxmox eventually
How come? I'm running proxmox currently but I'm considering just using a regular distro with lxd because I'm almost only using lxc containers...
Re: Start Self Hosting
#156This is why I'm building Timelinize [1]. It's a follow-up to my open source Timeliner project [2], which has the potential to download all your digital life onto your own computer locally, and projects it all onto a single timeline, across all data sources (text messages, social media sites, photos, location history, and more). It's a little different from "self hosting" but it does have a similar effect of bringing…
This sounds very cool, please submit a "Show HN" once the basics are working!
Re: Start Self Hosting
#157I'm not affiliated but I came across some software called Yunohost (https://yunohost.org/) recently, a Debian-based OS that tries to be user-friendly for self-hosting applications. Not sure how much it's being maintained.
Re: Start Self Hosting
#158Self hosting is hard. You need to take care of security, backups, software updates, software installation and so on. Even on something like a QNAP (which can be compared to managed hosting) this can be hard. Flip the wrong switch and you expose something to the world. Missed a security update: your device is now vulnerable. While I host a lot of things myself I can understand self hosting is not for everyone.
I used to love running my own servers with all the services etc. I’d manually write beautiful bash scripts to keep it all nice and easy to rebuild on the fly. My first job had 10 Ubuntu servers (on site) and I was the only guy who used Linux at home and had experience with sql. I have never volunteered to maintain servers since, it was horrible and everything was always my fault (it kinda was, I was a hobbyist at bes…
Sounds like you might've had an unusually bad experience. Might've also been the distro; I don't like Ubuntu much myself. :P
Maintaining inherited environments is also much more painful than ones you get to design from the ground up. I work with varied environments, and one with ~250 RHEL / CentOS machines has approximately the same level of maintenance burden as another with a dozen or so Ubuntus because the first environment has had configuration management from the beginning and the second is a complete mess that I've slowly tried to reverse-engineer and clean up.
When your change management works, maintaining a dozen servers isn't all that different from maintaining a thousand or more; and the need for change management and automation doesn't really go anywhere even when you don't self-host things.
Re: Start Self Hosting
#159I HATE the Spotify podcast player.
It is the worst UI for pretty much anything: music, video, podcast, lyrics ...
I selfhost ... i download the spotify exclusive podcasts and host them myself to use the with overcast. They come as OPUS files, but ffmpeg to the rescue.
Re: Start Self Hosting
#160Self-hosting is something that we should be constantly iterating on making easier; it's really the path forward for privacy centric folks. The main challenges are managing workload scheduling (SystemD is complicated for a layperson). Networking is another challenge; for instance, if you wanted all or part of these services to remain offline or on a Mesh VPN there's a lot of knowledge required. There's some projects t…
> 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…
> Is it? It has clean and logical abstractions, and consistency. Services depending in each other isn‘t complex or difficult to understand.
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.
Laypeople also aren't going to entertain the kind of pedantry that is systemd vs systemD vs System D vs SystemD so making systems that abstract further away from those communities is beneficial.
Edit: Thank you for your correction, as a systems engineer, but I couldn't help but highlight this is a big hurdle even in the Linux communities that I've been a part of as desktop Linux as gained wider adoption by laypeople.