Kamal 2 mastery
This course covers Kamal 2 configuration beyond one app on one server. It explains how a host is organized into kamal-proxy, app containers, role containers and accessories. Lessons show two applications sharing one host with hostname and path routing. They define web and worker roles with memory limits, and use destinations to run staging and production from one file. Later lessons cover remote builders and build cache, hooks such as a pre-deploy gate, rollbacks and deploy timeouts. The course ends with a complete production configuration.
What you'll learn
- ✓Running several apps behind one kamal-proxy, routed by hostname or path prefix
- ✓Defining roles with their own command, environment, memory limits and proxy setting
- ✓Using destinations, per-destination secrets and aliases for staging and production
- ✓Speeding up builds with a remote builder, registry cache and BuildKit secrets
- ✓Writing hooks, rolling back to retained images and tuning deploy timeouts
From one app to a fleet
The basics course got one application onto one server: kamal setup, a config/deploy.yml with a service, an image, a list of servers, a proxy with SSL, and a database accessory. That configuration is honest, and it stops being enough as soon as real requirements show up.
Read the full lesson free →Curriculum
7 lessonsFrom one app to a fleet
Describes where a single-app setup runs out, the containers on a Kamal host, and what Kamal does not do.
Two apps, one host
Runs two applications on one host through kamal-proxy, using distinct service names, hostnames, path prefixes and SSL certificates.
Roles: web, workers, and the rest
Explains roles as a map of servers, each with its own command, environment, memory limits and proxy setting.
Destinations: staging and production
Uses destinations to merge a staging file over the base configuration, with separate secrets, aliases and container names.
Builds that do not waste your afternoon
Speeds up builds with a remote amd64 builder and registry cache, and passes build credentials as BuildKit secrets.
Hooks, rollbacks, and bad deploys
Covers hooks such as a pre-deploy CI gate, rollback to retained images, migration limits and deploy timeout keys.
Putting it together: a production configuration
Combines two apps, a worker role, a staging destination, a remote builder and a pre-deploy gate into one configuration.