If you have needs beyond what Caddy offers, you setup a reverse proxy to Nginx. Let’s look at an example where you would use Nginx for caching. I also added a separate block, in case you want to pass reverse proxy it back to Caddy again.
You may wonder, wouldn’t it be simpler to just run Nginx in that case? Maybe, maybe not. It all depends on your needs.
In the example below I have a WordPress configuration where you could easily switch between passing the request to Nginx and passing it straight to PHP. You would simply change with_nginx to without_nginx. It also shows how you could support for purging URLs for the nginx cache, without exposing the purge URLs beyond access for localhost.
Here are some other posts you may like
A couple of weeks ago I looked into creating a generator that would output the php-code needed to embed javascript libraries hosted by cdnjs.com. As a part of doing this, I needed to create a searchable table that would filter rows as I typed. Since this table would hold a…
Electric power companies, in general, are pretty much the same. Tibber however, is unlike any electricity company I had seen before. They try to utilise the data we get from smart devices, which they also sell, to save electricity, money and the environment, as well as improving comfort. It’s a…
One of the recent introductions to the already versatile Home Assistant ecosystem is the Condition Selector for blueprints. At its core, this feature seems simple, but its implications for blueprint flexibility are profound. My usecase I've personally used this to update my smart lighting setup. I have one blueprint that…
