docs/docs/en/api/cli/proxy/caddy/generate.md
Generate or refresh the Caddy entry config for one CLI-managed env.
nb proxy caddy generate --env <name> [--host <domain>] [--port <port>]
| Parameter | Type | Description |
|---|---|---|
--env, -e | string | CLI-managed env name to generate the config for |
--host | string | Host written into the site address, such as app1.example.com |
--port | string | Listen port written into the site address, such as 8080 |
Using env test2 as an example, the command typically maintains these files and directories:
NB_CLI_ROOT/.nocobase/proxy/caddy/nocobase.caddyNB_CLI_ROOT/.nocobase/proxy/caddy/test2/app.caddyNB_CLI_ROOT/.nocobase/proxy/caddy/test2/public/index-v1.htmlNB_CLI_ROOT/.nocobase/proxy/caddy/test2/public/index-v2.htmlIn the current design, app.caddy is already the complete site config for one env and is no longer split into a separate generated.caddy file.
nb proxy caddy generate --env demo --host demo.local.nocobase.com
nb proxy caddy generate --env demo --host demo.local.nocobase.com --port 8080
generate only writes or refreshes config and does not automatically start Caddyapp.caddy as a wholeapp-port or app-public-path with nb env update, you will usually need to rerun this commandlocal or docker envs can use this command