Skip to content

Clarify Caddyfile placeholder timing #540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
steadytao wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −0
Open

Clarify Caddyfile placeholder timing #540

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/docs/markdown/caddyfile/concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -662,6 +662,8 @@ You can use any placeholders in the Caddyfile, but for convenience you can also

Not all config fields support placeholders, but most do where you would expect it. Support for placeholders needs to have been explicitly added to those fields. Plugin authors can [read this article](/docs/extending-caddy/placeholders) to learn how to add support for placeholders in their own modules.

Placeholders are usually evaluated at runtime by the module that supports them. This means they are not the same as Caddyfile parse-time features such as the [`import`](#snippets) directive or [Caddyfile environment variables](#environment-variables) (`{$ENV}`). Fields that are compiled or validated while the config is loaded, such as regular expression matcher patterns, may not support runtime placeholders as their input values. Use [`import`](#snippets) or [`{$ENV}`](#environment-variables) when you need to provide config text before the Caddyfile is adapted.




Expand Down