Update a pinned application source

A pinned-source deployment does not automatically use working-checkout edits. Select the correct reviewed release and rebuild the affected service from it. Read source selection.

Keep a recoverable source/data backup. Preserve other services and volumes. Do not rewrite a provenance manifest to make another file set appear valid.

Use the scoped production publication procedure. A plain or scoped restart preserves saved modes but does not rebuild production code. For a deliberate full release, bash restartDevServers.sh --prod rebuilds the selected production artifacts. Neither restart path runs schema initialization.

An already stopped, prepared service can use bash devstack.sh --prod start SERVICE; a running container is refused. Afterward, check service readiness and the affected user action. A changed source file does not by itself update the running application.

For a coordinated change of source, follow the full source-release procedure. Stop the selected deployment's writers before changing only ECS_APPLICATION_SOURCE_ROOT, then use bash startDevServers.sh --prod. Keep credentials, snapshots, data, keys, and schema mappings. Refuse destructive schema changes. Scoped commands retain the configured source pin. An old-source build does not establish acceptance for newer source.

The docs search hash reads only the canonical docs/en and docs/hu trees. Keep private agent artifacts outside published docs and search input.

For optional custom React views, read custom-runtime setup before activation.