@fideloper is right about Caddy, that's what I'd recommend too.
I know this is an older post but I suspect a lot of people end up here when they try to sort out custom domains in Laravel, so I figured it's worth coming back with some real world data. I can say, with experience*, that Caddy can very likely handle whatever scale you have, across distributed servers or a single server.
It might take a bit of learning and time, but in my opinion there's no open source server/cert manager out there that I think could do a better job at automating this than Caddy.
These are the things you'll likely need to spend a bit of time sorting out:
- exactly what you want your config to look like (just subdomains or apex domains too? custom headers? etc.)
- how you want to update (push or pull? on change or batched?)
- how you want to monitor it (things happen, issues mean custom domains are down)
- have a process for when things don't go right (certs get revoked by CAs, CA ratelimits, etc.).
- Caddy goes a long way helping you here but if you have much scale at all, you'll likely run into these things sooner than later.
* Source:
I'm the founder and developer of https://approximated.app, which is a managed service to handle custom domains for those that don't want to build or maintain this themselves. It reliably serves hundreds of thousands of domains, millions of requests per month, and terabytes of traffic, and part of what we use is a customised version of Caddy under the hood.
Anyone who's looking to add custom domains to their Laravel app, I've also put up an example Laravel app repo where you can see some examples of how to handle the routing/middleware/etc. for custom domains.
