Comment on Self-hosting is having a moment. Ethan Sholly knows why.
jeena@piefed.jeena.net 2 weeks ago
I wanted to ask where the border of selfhosting is. Do I need to have the storage and computing at home?
Is a cheap VPS on hetzner where I installed python, PieFed and it's Postgres database but also nginx and letsencrpt manually by mydelf and pointed my domain to it, selfhosting?
It depends who you ask (which we can already tell hehe), but I’d say YES, because you’re the one running the show – you’re free to grab all of your bits and pieces at any time, and move to a different provider. That flexibility of not being locked into some provider that can suddenly take a bad turn, is what’s precious to me.
And on a related note, I also make sure that this applies to my software-stack too – I’m not running anything that would be annoying to swap out if it turns bad.
It’s self hosting as long as you are in control of the data you’re hosting.
I would say there’s no value in assigning such a tight definition on self-hosting–in saying that you must use your own hardware and have it on premise.
I would define selfhost as setting up software/hardware to work for you, when turn-key solutions exist because of one reason or another.
Netflix exists. But we selfhost Jellyfin. Doesn’t matter if its not on our hardware or not. What matters is that we’re not using Netflix.
Your stuff is still in the cloud, so I would say no. It’s better than using the big tech products, but I wouldn’t say it’s fully “self hosted”. Not that that really makes much of a difference. You’re still pretty much in control of everything, so you should be fine.
Where is the tipping point though? If I have a server at my parents house, they live in Germany and I in Korea, does my dad host it then because he is paying for the electricity and the access to the internet and makes sure those things work?
Your parents’ house isn’t the cloud, so yeah, it’s self hosted. The “tipping point” is whether you’re using a hosting provider.
They are using a hosting provider - their dad.
“The cloud” is also just a bunch of machines in a basement. Lots of machines in lots of “basements”, but still.
Isn't my dad the hosting provider? I ordered the hardware, he connected it to his switch and his electricity and pressed the button to start it the first time. From there on I logged in to his VPN and set up the server like I would at Hetzner.
But you're right it doesn't really make a difference. I feel the only difference it makes for me where I post my questions on Lemmy if it is in a !selfhosting community or a !linux community.
From a feeling perspective, even if I use Hetzners cloud, I feel I self host my single user PieFed instance (and matrix, my other websites, mastodon, etc.) because I have to preform basically the same steps as for things I'm really hosting at home like open-webui, immich, peertube.
Self hosting just means maintaining your own Instance of a web service instead of paying for someone else‘s
As long as you dont pay hetzner for an explicit fully maintained Nextcloud server, it dosent matter if the OS you‘re running it on is a VM or a bare bones server
Is a cheap VPS on hetzner where I installed python, PieFed and it’s Postgres database but also nginx and letsencrpt manually by mydelf and pointed my domain to it, selfhosting?
I don’t get hung up on the definitions and labels. I run a hybrid of 3 vps and one rack in the closet. I’m totally fine with you thinking that is not selfhosting or homelabbing. LOL I have a ton of fun doing it, and that’s the main reason why I do it; to learn and have fun. It’s like producing music, or creating bonsai, or any of the other many hobbies I have.
Why wouldn’t you just use Docker or Podman
Yeah why wouldn’t you want to know how things work!
I obviously don’t know you, but to me it seems that a majority of Docker users know how to spin up a container, but have zero knowledge of how to fix issues within their containers, or to create their own for their custom needs.
That’s half the point of the container… You let an expert set it up so you don’t have to know it on that level. You can manage fast more containers this way.
OK, but I’d rather be the expert.
And I have no troubling spinning up new services, fast. Currently sitting at around ~30 Internet-facing services, 0 docker containers, and reproducing those installs from scratch + restoring backups would be a single command plus waiting 5 minutes.
I use apps on my phone, but have no clue how to troubleshoot them. I have programs on my computer that I hardly know how to use, let alone know the inner workings of. How is running things in Docker any different? Why put down people who have an interest in running things themselves?
I know you’re just trying to answer the above question of “why do it the hard way”, but it struck me as a little condescending. Sorry if I’m reading too much into it!
No, I actually think that is a good analogy. If you just want to have something up and running and use it, that’s obviously totally fine and valid, and a good use-case of Docker.
What I take issue with is the attitude which the person I replied to exhibits, the “why would anyone not use docker”.
I find that to be a very weird reaction to people doing bare metal. But also I am biased. ~30 Internet facing services, 0 docker in use 😄
You can customize or build custom containers with a Dockerfile
I did that first but that always required much more resources than doing it yourself because every docker starts it's own database and it's own nginx/apache server in addition to the software itself.
Now I have just one Postgresql database instance running with many users and databases on it. Also just one Nginx which does all the virtual host stuff in one central place. And both the things which I install with apt and manually are set up similarly.
I use one docker setup for firefox-sync but only because doing it manually is not documented and even the docker way I had to research for quite some time.
What? No it doesn’t… You could still have just one postgresql database if you wanted just one. It is a big antithetical to microservices, but there is no reason you can do it.
But then you can't just use the containers provided by the service developers and have to figure out how to redo their container which in the end is more work than just run it manually.
Personally, I’d say no. At that point you are administering it, not hosting it yourself.
I’d say you need storage. Once you get storage, use cases start popping up into view over time.
smiletolerantly@awful.systems 2 weeks ago
I would say yes, it’s still self-hosting. It’s probably not “home labbing”, but it’s still you responsible for all the services you host yourself, it’s just the hardware which is managed by someone else.
Also don’t let people discourage you from doing bare-metal.
stefenauris@pawb.social 2 weeks ago
That’s actually a good point, self hosting and home lab are similar things but don’t necessarily mean the same thing
grrgyle@slrpnk.net 1 week ago
Interesting distinction. I use a small managed vps, but didn’t consider that self-hosting, personally. I do aspire to switch to a homelab and figure out dynamic DNS and all that one day.