What's New
New updates and improvements to Hatchbox.io
← BackCaddyfile Support! 🎉
New
Today, we're releasing an update that changes over to using the Caddyfile format for all apps on Hatchbox.
Customizing Caddy has been historically painful because we've used the JSON syntax to talk to Caddy's API. The JSON format is what's used internally by Caddy, but it's not very user friendly. We've refactored the internals of Hatchbox to use the Caddyfile syntax and provided some variables to include our default configurations but also make it easy to mix and match your own as needed.
Clusters have a Caddyfile option for defining global options. Apps have a Caddyfile option for how requests are processed for that specific app. These are then combined when the Caddy config is uploaded to your server.
We will help you convert it over to the Caddyfile syntax if you've customized your apps already. Our plan is to get everyone moved over and get rid of the complex JSON once and for all. Send us a message and we'll help get you migrated.
Customizing Caddy has been historically painful because we've used the JSON syntax to talk to Caddy's API. The JSON format is what's used internally by Caddy, but it's not very user friendly. We've refactored the internals of Hatchbox to use the Caddyfile syntax and provided some variables to include our default configurations but also make it easy to mix and match your own as needed.
Clusters have a Caddyfile option for defining global options. Apps have a Caddyfile option for how requests are processed for that specific app. These are then combined when the Caddy config is uploaded to your server.
We will help you convert it over to the Caddyfile syntax if you've customized your apps already. Our plan is to get everyone moved over and get rid of the complex JSON once and for all. Send us a message and we'll help get you migrated.