• 0 Posts
  • 392 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle


  • I never went too far down the nginx route, so I can’t really compare the two. I ended up with caddy because I self-host vaultwarden and it really doesn’t like running over http (for obvious reasons) and caddy was the instruction set I found and understood first.

    I don’t make a lot of what I host available to the wider internet, for the ones that I do, I recently migrated to using a Cloudflare tunnel to deal with the internet at large, but still have it come through caddy once it hits my server to get ssl. For everything else I have a headscale server in Oracle’s free tier that all my internal services connect to.





  • I think you can also use

    services:
      vaultwarden:
        expose: 
          - 80
    

    And use 80 instead of 11808 in the caddy file.

    Then the port will be available internally for caddy but not to the outside world. That may also need a network created in docker though. I’m on my phone so I can’t check the finer details at the moment.