I mean, I'd rather not.
daFRAKKINpope
joined 2 years ago
I know it used to. No clue if Apple patched it out in the decade since I've tried tho.
"Our destination is just over the next hill. Now let's listen to the radio or I'll turn this car around."
My dad, probably.
Touch screens are a pox upon vehicles, and need to be removed.
Then I will scream from the rooftops.
No one will listen to me, because everyone important is making money off the current system. But I'll try.
I'd never thought of this. This is a great idea. You need to shout it from the rooftops.
I'm reading about Caddy and playing around with it. It seems pretty straightforward. I'll have to see if I can't implement it.
This is valuable feedback. In retrospect I didn't explain my problem at all. I'm really good at reading instructions, pretty poor at asking for help.
I'm going to take another crack at this, after I read up on and learn all about Caddy. At first glance it looks like it takes away a lot of my pain points from Traefik.
I host in the way that you describe: "service.domain.com". I use Cloudflare, docker, and Caddy.
I don't remember any pit falls off the top of my head. Make sure to use HTTPS (port 443). Everything on http is basically open for everyone to see. Caddy should set that up for you automatically, tho. I recently moved to Caddy from Traefik, it's an awesome tool.
Oh, here's a pitfall. One time I opened a port, #22, for ssh access to my server. I installed fail2ban on my server. One weekend I looked at my logs and found I'd banned hundreds of IP addresses. Some bot found my open port and then begun attacking the login with some kinda rainbow table. I moved the port from the ssh default to something else and never had a problem since.
Also, and this isn't a requirement but just useful, I set up a VLAN for my selfhosted server. It's firewalled from my local network. That way, if someone access' my server they don't have access to my whole network.
So, tldr, have fun and midigate risk where you can.