corestack_ files_ sync
Sync an archive into the site.
When to use it
Unpack an uploaded archive (tar, tar.gz, tar.zst or zip; corestack_transfer_upload_create) into a path under the site root (htdocs, a path under it, or shared/…) as the site user. Everything is checked and staged before the site is touched; the platform's own files (wp-config.php, .env, app/etc/env.php, the WordPress loader) are never overwritten or deleted. delete_extraneous removes files the archive does not have, except paths an exclude matches. On a Git-mode site switch to manual deployment first (corestack_deployments_mode_set).
Ask for it
Using the Corefinity MCP server, call corestack_files_sync with site_id 4211, transfer_id 2207, target_path /var/www/example.co.uk/htdocs. (Sync an archive into the site.) Tell me what it returned.Inputs
The site's domain, typed exactly, to delete on production. Up to 253 characters.
Defaults to false.
rsync patterns: never written, never deleted. Up to 100 items.
At least 1.
Defaults to 0. 0 to 5.
Relative to the site root, e.g. htdocs. Up to 1,024 characters.
At least 1.
Your assistant fills in a confirmation only after you agree.
Example call
{
"name": "corestack_files_sync",
"arguments": {
"site_id": 4211,
"transfer_id": 2207,
"target_path": "/var/www/example.co.uk/htdocs"
}
}If it is refused
| Reason | What to do |
|---|---|
git_mode | A files sync into the releases layout of a Git-mode row; switch the site to manual deployment first (corestack_deployments_mode_set). |
archive_member_refused | An archive member's name, type or link target is refused; details names the member; nothing written; repack without it. |
archive_too_large | The archive's entries or expanded bytes are over mcp.files.max_entries / mcp.files.max_expanded_bytes; split the archive. |
format_unsupported | The archive is not tar, tar.gz, tar.zst or zip, a zip uses zip64, encryption or a method other than stored / deflate, or the helper's PHP module would not load in the no-php.ini run — ended at its first step, nothing downloaded or written; repack it. |
insufficient_space | The row's disk cannot hold the files sync's expanded tree, or a path database export would take the volume's free space under mcp.files.space_margin_bytes; free space or raise the package. |
transfer_changed | The transfer's object is not the generation recorded for it, or yields more bytes than its scan did; nothing was written; upload again. |
unsafe_link | The destination holds a symlink the sync would write through that is not one of the row's shared-path links; details names it; nothing written; remove or replace the link, then call again. |
transfer_cancelled | A consuming run was stopped — or stopped itself at its last check before anything destructive — because the transfer it was using was cancelled, whichever grant ran it; an import's safety snapshot is its way back, a sync's stage is removed; upload the file again if it is still wanted. |
managed_elsewhere | Another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done. |
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. |