You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently go templates only take effect on tag values. Can it be extended to take effect on external Caddyfile?
Consider one or more long snippets. It is inconvenient to write and read when defined in a tag. It is more convenient to define it directly in an external Caddyfile, but it will lose the support of go templates.
The text was updated successfully, but these errors were encountered:
The troublesome thing is some users might want to literally use Go templates in their respond directive since Caddy has the templates directive, so if it was processed already when producing the Caddyfile, it would break those templates. So 🤷♂️
Could it be limited to processing only templates starting with a specific string? What I mean is: only process {{.CaddyDocker.Spec.Name}}, skip not starting with CaddyDocker.
Currently go templates only take effect on tag values. Can it be extended to take effect on external Caddyfile?
Consider one or more long snippets. It is inconvenient to write and read when defined in a tag. It is more convenient to define it directly in an external Caddyfile, but it will lose the support of go templates.
The text was updated successfully, but these errors were encountered: