pylon start launches the Pylon daemon — an HTTP server that listens for incoming webhooks and runs scheduled cron jobs. It powers up every pipeline you’ve constructed (or a single named one) and keeps running until you stop it.
Usage
Arguments
Optional. Start only the named pylon instead of all constructed pipelines. Useful for testing a single pipeline in isolation.
Startup sequence
When you runpylon start, Pylon:
- Loads
~/.pylon/config.yamland~/.pylon/.env - Loads all pylon configs (skips disabled ones)
- Recovers any jobs that were pending when the daemon last stopped
- Prunes orphaned Docker containers and workspaces from previous runs
- Builds or verifies agent Docker images
- Starts the HTTP server on the configured host and port (default
0.0.0.0:8080) - Watches pylon config files for changes and hot-reloads them automatically
Stopping the daemon
Press Ctrl+C in the terminal, or sendSIGTERM to the process. Pylon shuts down gracefully.
pylon stop and pylon restart print instructions — they do not signal the running process directly. To control the daemon as a background service, use systemd.
Hot reload
Pylon watches~/.pylon/pylons/*/pylon.yaml for changes. When you save a pylon config (e.g. via pylon edit), the daemon reloads it automatically without a restart.
Changes to
~/.pylon/config.yaml (the global config) require a full daemon restart.Concurrency
Pylon runs up todocker.max_concurrent agent containers in parallel (default: 3). Jobs that arrive when all slots are occupied are currently rejected. Increase the limit in ~/.pylon/config.yaml: