Nice. My partner has a Proxmox setup, so we've adapted the Nix config to spin up new VMs of any machine with a single command.
smiletolerantly
joined 1 year ago
NixOS :)
Maybe I should have clarified that liking bare-metal does not imply disliking abstraction
Containers != services.
I don't think I am better than anyone. I jumped into these comments because docker was pushed as superior, unprompted.
Installing and configuring does not an expert make, agreed; but that's not what I said.
I would say I'm pretty knowledgeable about the things I host though, seeing as I am a contributor and / or package maintainer for a number of them...
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.
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.
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 😄
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.
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.
To clone their voice, and to send the audio to some unknown server
Which shouldn't really be an issue since you should only host on 443, which tells bots basically nothing.
Configure your firewall/proxy to only forward for the correct subdomain, and now the bots are back to 0, since knowing the port is useless, and any even mildly competent DNS provider will protect you from bots walking your zone.
Sorry, saw this only just now. I don't really have any guides to point to, so just the basic steps:
- host jellyfin locally, e.g. on http://192.168.10.10:8096/
- configure some reverse proxy (nginx, caddy, in my case it's haproxy managed through OPNSense)
- that proxy should handle https (i.e. Let's Encrypt) certificates
- it should only forward https traffic for (for example) jellyfin.yourdomain.com to your Jellyfin server
- create a DNS entry for jellyfin.yourexample.com pointing either to your static IP, or have some DynDNS mechanism to update the entry
90% of this is applicable to any "how to host x publicly" question, and is mostly a one-time setup. Ideally, have the proxy running on a different VM/hardware, e.g. a firewall, and do think about how well you want/need to secure the network.
In any case, you then just put in https://jellyfin.yourdomain.com/ in the hotel TV.
YES, WATCH STEINS;GATE!
Not Steins;Gate Zero though, that's a sequel.
The most common criticism is that the first handful of episodes are slow, but I hard disagree. Every moment is either re-contextualized later on, or is important character work.