Staging and locked configuration¶
Configuration is deployed from git, so tools classified as config writes only run where configuration is writable:
- With Config Read-only
installed, config is writable when
$settings['config_readonly']is not TRUE. - Without it, config is writable when settings.php sets
$settings['site_agent_allow_config_writes'] = TRUE;. The default is FALSE.
Where config is locked, config-write tools are left out of the model's tool list and refused if called.
Staging¶
A development site stages content: where configuration is writable and
Content Deployment's content_deployment_export is installed, with
Workspaces. There:
- A new thread keeps the workspace active when it starts, whichever workspace later requests have active. Its content calls, reads included, run in that workspace; configuration writes run outside any workspace.
- A thread started in Live writes no content: the call is refused with a message to switch to a staging workspace and start a new conversation.
- Cards and Publish work in the thread's workspace. A result card compares the workspace's version with what visitors see, and calls content that isn't published in the workspace a draft, since an export leaves it out.
- The chat names the workspace and, for accounts with
export content deployment changesets, links to its Export changeset form. An export is the approval to publish what it carries, so no tool makes it.
Live sites, where configuration is locked, use no workspace. Threads and tool-call records are ignored by Workspaces, so they save whichever workspace is active.