Collabhost v1.6.3
Patch release with three fixes on top of v1.6.1.
Fixes
- Static-site runtime config now survives upgrades. Operator edits to a static site's runtime configuration file are written to a persistent location and served on top of the deployed assets, so they are no longer lost when the app's files are replaced during an upgrade. Setting a value through the API on a read-only install now succeeds instead of failing.
- Runtime-config writes work over both the REST API and the MCP server. The writer that applies runtime-config changes is now wired on both control surfaces, not just one.
- Starting an app over MCP refreshes technology probes. Starting a routing-only app through the MCP server now refreshes its probe-derived metadata the same way the REST API does, so the app's reported technology details stay current.
The bundled Caddy version is unchanged from the v1.6.x line.
Upgrading
If you set a runtime configuration override on a static site under an earlier version (for example, a portal's config.json API address), re-apply it once after upgrading. This release serves that file from a persistent location through a new proxy route; if the value was registered on an older version but never written to disk, the config path returns 404 until you re-save it, and a single-page app that depends on it will fail to load with a blank page.
To re-apply: read the site's runtime configuration values, then save the same values back — through the dashboard settings page or the get_settings / update_settings MCP tools. No restart is required; the file is written when the setting is saved. Then confirm the config path returns 200 with the expected content and the app loads. Fresh installs and overrides that were already on disk are unaffected.