corestack_ nginx_ snippets_ list
nginx snippets.
When to use it
The nginx snippet library for an environment row's platform: each snippet's parts (hook, content, placement) and placeholders, whether the row can use it now, and otherwise which hooks or capabilities it waits for (the one-time update). Insert every part of a snippet into one corestack_nginx_rules_update.
The rate-limit snippets (rate-limit-*) are listed only for an environment whose runtime supports the platform rate-limit presets; on any other they are left out rather than shown as waiting.
Ask for it
Using the Corefinity MCP server, call corestack_nginx_snippets_list with site_id 4211. (nginx snippets.) Tell me what it returned.Inputs
The environment row. At least 1.
Example call
{
"name": "corestack_nginx_snippets_list",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
Path apps
The list also holds the path app presets: entries with category path-apps and kind path_app, whose preset holds the record fields they pre-fill (WordPress admin for FishPig, WordPress full, legacy PHP directory, static directory, another site (proxy), single PHP entry, IP or host gate). They have no nginx parts: add the record to path_apps in corestack_nginx_rules_update (with its preset key), filling in what the preset leaves to you, such as a legacy directory's PHP files, a gate's addresses or another site's proxy.url. The proxy-site preset is listed whether or not this environment's runtime takes a proxy yet; corestack_nginx_rules_get's path_apps.proxy_available says whether it does.