With Hatchbox, you have the ability to fully control how Caddy processes requests. By default, Caddy is configured to handle SSL, serve static files, and reverse proxy everything else to your application running on the specified PORT.

You can customize each application individually as well as configuring global settings on the cluster to enhance logging and other settings.

Read the Caddyfile documentation to learn more about customizing Caddy.

Customizing Caddy settings for Applications

Under your application's Settings, you'll find a Caddyfile section that you can use to customize how Caddy handles requests. You will find a list of variables you can use in the configuration. A few example variables are:

%{log} - enables request logging for this app
%{root} - sets the root folder location for this app
%{asset_cache_control} - Adds Cache-Control="public, max-age=31536000" headers to /assets/* and /packs/*
%{hatchboxapp_robots} - Adds a robots.txt for the app's assigned hatchboxapp.com subdomain so it doesn't get indexed by search engines
%{error_handler} - Handles error responses from the upstream application and serves a friendly error page
%{encode} - Enables compression of responses
%{file_server} - Serves static files to the client
%{reverse_proxy} - Forwards HTTP requests to the application

See your app's Settings page for the full list.

For example, if you'd like to cache static files, you can add a matcher and header directive. Adding this before the %{default} variable will ensure it applies before the base configuration. This will apply the Cache-Control header to any requests ending in these file extensions and the default configuration will serve those static files.

@static_files {
    path *.ico *.css *.js *.gif *.webp *.avif *.jpg *.jpeg *.png *.svg *.woff *.woff2 *.map *.swf *.flv
}
header @static_files Cache-Control "public, max-age=31536000"

# Use the default configuration for everything else
%{default}

Customizing global Caddy settings on Clusters

You can also customize global settings on the Cluster level as well as manually include any additional app configuration. At the cluster level, there are a few variables for setting the trusted proxies for load balancers and inserting the Hatchbox applications into the config.

%{trusted_proxies} - a list of trusted proxy addresses used for the trusted_proxies Caddy configuration
%{apps} - inserts the Caddy configuration blocks for each Hatchbox application

Caddy Options on Hatchbox

Customizing Caddy settings for Applications

Customizing global Caddy settings on Clusters