How to migrate a Caddyfile with wildcard site and host matchers to Ferron?

[krovuxdev]

Hello,
I want to start using Ferron, but I have some doubts about how to properly migrate my current Caddy configuration.

In Caddy, I use a wildcard site (*.example.com) and then route traffic to different services based on the host using named matchers. I like this approach because I can keep everything under a single wildcard domain.
Here is a simplified example of my current Caddyfile:

{
    admin 0.0.0.0:2019
}

*.example.com {
    tls internal
    tls {
        dns cloudflare {env.CLOUDFLARE_API_TOKEN}
        propagation_delay 2m
        resolvers 1.1.1.1
    }

    @foo host foo.example.com
    reverse_proxy @foo backend_foo:8008

    @bar host bar.example.com
    reverse_proxy @bar backend_bar:8001
}

My questions are:

• Is it possible to achieve a similar setup in Ferron using a wildcard domain (*.example.com)?
• What is the recommended way to translate Caddy named matchers (@foo, @bar) into ferron.kdl?
• Should each subdomain be defined explicitly, or is there a cleaner pattern for this kind of configuration?

Thanks

[DorianNiemiecSVRJS]

Is it possible to achieve a similar setup in Ferron using a wildcard domain (*.example.com)?

Yes, Ferron support wildcard domains

What is the recommended way to translate Caddy named matchers (@foo, @bar) into ferron.kdl?

You can use conditionals for that, like:

// Example of using conditionals in Ferron configuration.
example.com {
  condition "IS_API" {
    is_regex "{path}" "^/api(/|$)"
  }

  if "IS_API" {
    proxy "http://127.0.0.1:3000"
  }

  if_not "IS_API" {
    root "/var/www/html"
  }
}

You can learn how to use the conditionals in https://ferron.sh/docs/configuration-kdl (it's the configuration reference by the way).

[krovuxdev]

@DorianNiemiecSVRJS This works for me 🙂. By the way, I can’t find anything in the documentation about something like this:

tls internal
tls {
    dns cloudflare {env.CLOUDFLARE_API_TOKEN}
    propagation_delay 2m
    resolvers 1.1.1.1
}

Also, do you think it would work with this?

{
    admin 0.0.0.0:2019
}

[krovuxdev]

tls internal  Generates a self-signed TLS certificate using Caddy's own internal CA (Certificate Authority), without requesting one from Let's Encrypt.

admin 0.0.0.0:2019  Exposes a REST API to reconfigure Caddy in real time without restarting it, accessible from any machine on the network.

dns cloudflare  Allows Caddy to automatically manage the DNS-01 challenge on Cloudflare to obtain wildcard certificates.

propagation_delay Waits for the DNS to propagate the TXT record before Let's Encrypt verifies it.

resolvers Uses Cloudflare's DNS resolver to verify that the TXT record is already visible.

env in Ferron Environment variable support is not yet available in Ferron, but it is being worked on in PR #425. I will wait for it to be merged, hopefully it will.

These were missing — Ferron does not support them yet.