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.

  • anytimesoon@feddit.ukOPEnglish
    0·
    4 months ago

    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

    • Oisteink@feddit.nlEnglish
      1·
      4 months ago

      No - ssh is very easy to secure, while an exposed web-service is very hard to secure. Theres no difference in the security of ssh without password and for example WireGuard.

    • tburkhol@lemmy.worldEnglish
      0·
      4 months ago

      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.

        • tburkhol@lemmy.worldEnglish
          1·
          4 months ago

          I just don’t like my logs filling up with scripted login attempts. Even with fail2ban, for a while there I was getting 100+ login attempts every day, and it upset my sense of order.