Caddy(8)

🌸 NAME 🌸

caddy-run — starts the Caddy process and then just... blocks. forever. indefinitely. it's giving loyal.

---

✨ SYNOPSIS ✨

caddy run [--config  [--adapter ]] [--envfile ] [--environ] [--resume]
[--watch] [--pidfile ] [flags]

---

💖 DESCRIPTION 💖

okay so bestie, picture this: you run caddy run and Caddy wakes up, optionally with an initial config file to bootstrap it, and then it just stays there. Like, blocks indefinitely until the server is stopped. That's "daemon" mode, but in the foreground. main character energy honestly, it doesn't leave the room. 👑

If you hand it a config file, that file gets applied immediately once the process is already running. And if your config file is not in Caddy's native JSON format, no stress — you can name an adapter with --adapter and it'll adapt your file into Caddy's native format for you. That adapter has to be a registered module though, fr fr. Any warnings will get printed to the log, but ⚠️ beware: any adaptation that comes out without errors is immediately used. If you wanna peek at the adaptation results before committing, run the adapt subcommand first. so smart of you.

Special case, and it's kind of iconic: if your current working directory has a file literally called "Caddyfile", and the caddyfile config adapter is plugged in (it is by default, bestie), then that file gets loaded and used to configure Caddy — even if you passed zero command line flags. it just knows. 🔮

If you pass --envfile, an environment file full of environment variables in KEY=VALUE format gets loaded into the Caddy process. cute.

If you pass --environ, the environment as seen by the Caddy process gets printed before starting. it's the same as the environ command, except it does not quit after printing — which is super useful for troubleshooting. 🩺

About --resume: it will override the --config flag if there's a config auto-save file hanging around. And listen, it is not an error if you use --resume and no autosave file exists. no drama. 🫶

And if you pass --watch, the config file gets loaded automatically after changes. ⚠️ but caution bestie, this can make unintentional config changes easier — only use this one in a local development environment. please. for me. 🙈

---

🎀 OPTIONS 🎀

• -a, --adapter="" — name of the config adapter to apply
• -c, --config="" — the configuration file
• --envfile=[] — environment file(s) to load
• -e, --environ[=false] — print the environment
• -h, --help[=false] — help for run
• --pidfile="" — path of the file to which the process ID gets written
• --pingback="" — echo confirmation bytes to this address on success
• -r, --resume[=false] — use the saved config, if any (and prefer it over the --config file)
• -w, --watch[=false] — watch the config file for changes and reload it automatically

---

🦋 SEE ALSO 🦋

• caddy(8)

---

👑 HISTORY 👑

• 1-Jan-0001 — auto generated by spf13/cobra

---

so that's the whole page bestie, no cap 💅 and for the cute sign-off: this lil masterpiece is auto generated by spf13/cobra, stamped Jan 0001, and it belongs to the Caddy(8) manual. periodt. 🌈✨🍓