Absolutely! Subdomain all the things!. As long as it's at a different port you're good to go

Why cloudflare tunnels? If you already have a domain, and are going to use cloudflare, why add their dns nameservers to your registrar admin page, and use their dns for free?? That solves the issue of hosting at home and showing your ip to the world via any method using your domain name, all they'll see is cloudflare.

for the shell, that's an easy one, shellinabox, with a custom dark mode.

for the exposed services you describe, none are "exposed", they are hosted in nginx (meant to face the WAN, subdomained and not port forwarded) with fail2ban setup for custom filtering, and beyond that are proxied through cloudflare and their filtering for ddos etc. Most of my services are behind htpasswd hashed/salted pw's or ldap (right now just htpasswd for the local site), and the ones that arn't use token logins like plex, overseerr, etc. I'll be ok :)

lSIO is amazing, my first stop for container browsing! Followed in second place by hotio.dev

Very cool site! You're so right, hosting at home is so fun and actually super useful! My setup is soooo much easier to access and control now, and I've learned so much.

My self hosted site is at https://nintenuendo.tv heh, cheers to many more years of open-source!

Really slick and personally helpful to sooo many people, what an insanely awesome project!

Hooooooooooly shit, this is amazing, I will use the ever loving hell out of this. Awesome project!

Yeah I gave up on handling collections manually, wayyyyy too much work.

Introducing: Plex Meta Manager

go this rout, and don't look back

This to me sounds like something that NextCloud is built for. Instead of building something piece by piece with github repos it might just be easier to switch your service platform to something that already has features like that built in.