• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: February 17th, 2024

help-circle















  • That can be done transparently, just by using a key with no password (or using your account password for the key, so that when you log in it decrypts, and keeps the session open on your device).

    The bigger problem is key management. You can’t allow the server to know your private key else the admin could steal it. So it has to stay on your device, and if you lose your device or accidentally delete the key, your account is gone.



  • It does a couple things. It’s one service that routes requests to multiple services. So if you have radarr, sonarr, etc., you can put a reverse proxy in front and use the same ip-port to connect to all, and the proxy routes the request to the service by hostname.

    If you have multiple instances of the same service for HA, it can load balance between them (though this is unlikely for a homelab).

    Personally I run all my services through docker and put traefik in front, so that I don’t have to keep track of ports. It’s all by name.

    It’s also nice because traefik handles HTTPS termination, so it automatically gets certs for each name, and the backing service never needs to worry about it (it’s http on the backend, but all that traffic is internal).