Dockge allows you to start/stop containers and edit your compose files from a handy ui.
Pros: if something goes wrong while you’re away, it would give you a tool to restart a service or make some changes if necessary.
Cons: exposing that much control to the outside world (even behind a log in) can potentially be catastrophic for your stack if someone gets in.
I could see that, but I would also have to ask ‘what exactly do we gain by having access to these tools when we aren’t home?’
I used to try to do all of that but I started to realize, I spend too much time dealing with broken shit. Coming to the mindset of if I’m not home and it doesn’t work then oh well has been one hell of a stress relief for me
Yeah, I think it really depends on use case. Like, I’m trying to imagine what aspect of my home lab could go so wrong, while I’m out of the house, that it would need fixed right away, and there’s nothing. I only leave my house for work or maybe a week of vacation, though, and I can imagine someone who’s occasionally away from home/house for 6-month deployments, or has a vacation home they only visit four weekends a year, might want more extensive remote maintenance. I’d still want to do that via ssh or vpn, but that’s me.
This is pretty much my situation. “Away from home” for me isn’t just a trip to the shops, it means being away for weeks at a time. I need to be able to fix things remotely if needed.
I’ve seen people recommend SSH, which seems worse because that would give potential hackers access to the whole system.
VPN is a very good suggestion, and what I’ve implemented now. Thank you to everyone who contributed
I do ssh because I’m more comfortable with it: it’s ubiquitous and as close to bulletproof as any security. Put it on a nonstandard port, restrict authentication to public keys, and I have no qualms.