[deleted]

Comments

• uranibaba@lemmy.world ⁨7⁩ ⁨months⁩ ago

  Here is two enteries from my Caddyfile:

  ip.domain.tld:80 {
          respond "{client_ip}" 200
  }
  
  
  git.domain.tld {
          reverse_proxy forgejo:3000
  }
  

  This is all I need and Caddy will handle the rest. I have created a network with podman/docker that I add to any container that I need to reverse proxy to.

  source
• MangoPenguin@piefed.social ⁨7⁩ ⁨months⁩ ago

  Without using a domain a reverse proxy doesn't really make sense to use, since you're just using direct IP addresses.

  source
• bulwark@lemmy.world ⁨7⁩ ⁨months⁩ ago

  I also use Traefik, and once you have it set up it’s really great. Getting it set up is a different story. My advice would be to follow the install guide as closely as you can and don’t start adding to it until it’s stable.

  You don’t need to own a domain to use a reverse proxy by the way, you just need to configure your router to recognize whatever domain you choose and route it to the container.

  Lately, I’ve been playing around with Tailscale and you don’t even need a domain or open ports to connect to your containers from outside your local network.

  source

  • undefined@lemmy.hogru.ch ⁨7⁩ ⁨months⁩ ago

    I recently wrote a Caddyfile for a Dockerized Ruby on Rails application in a Kubernetes cluster using Traefik. Traefik connects to Caddy via h2c and Caddy talks to Puma in Ruby on Rails via HTTP/1.1 over UNIX socket.

    I bring this all up because I think h2c is very underutilized and this led to a huge increase in performance.

    source

    • bulwark@lemmy.world ⁨7⁩ ⁨months⁩ ago

      I’ve never heard of h2c but it seems useful. I use docker swarm with a few nodes. But for internal communication all the containers can communicate with each other using docker’s built-in DNS.

      I run Traefik in front of Caddy for a few different applications including Nextcloud.

      source
• _cryptagion@anarchist.nexus ⁨7⁩ ⁨months⁩ ago

  Why use Caddy at all then? Tailscale would work just as well, with the added bonus that you could access it outside your LAN without exposing it to the clearnet.

  source
• sturlabragason@lemmy.world ⁨7⁩ ⁨months⁩ ago

  How about traefik?

  source

  • jobbies@lemmy.zip ⁨7⁩ ⁨months⁩ ago

    [deleted]

    source

    • ijhoo@lemmy.ml ⁨7⁩ ⁨months⁩ ago

      Once you figure out how traefik is configured, this is super logical and easy. Also, you can use it with podman and qublet on fedora, so you can manage it all with systemd.

      theobservum.com/posts/2023/2023-04-15_traefik/

      Tldr; Traefik is looking at all containers and scans for labels (attributes on containers). If certain labels are set, Traefik adjust itself. So the trick is how to set those labels, which both docker compose and qublet make easy, but qublet doesn’t need a compatibility package and comes natively with podman.

      source
    • cron@feddit.org ⁨7⁩ ⁨months⁩ ago

      I’ve run caddy and traefik. Personally, I prefer caddy, but both are likely completely fine for your use case.

      Traefik has the advantage that it can be configured with docker compose files, while caddy needs its Caddyfile as a seperate configuration.

      source
• illusionist@lemmy.zip ⁨7⁩ ⁨months⁩ ago

  What do you use caddy for without domains?

  source

  • bender223@lemmy.today ⁨7⁩ ⁨months⁩ ago

    that’s a good point. I’ve only used caddy for handling certs for all the docker containers on my server. for local uses, you generally don’t need certs, although there are some apps that communicate with an offsite db that requires a secure connection.

    source