Deploying an update

Use the project's deployment script:

./bin/deploy.sh              # deploy
./bin/deploy.sh --dry-run    # show the planned changes

Set DEPLOY_HOST and DEPLOY_ROOT to target another installation.

The script stops the service, installs dependencies, builds the application, applies migrations, synchronises the release, sets ownership, and starts the service. Do not replace selected files by hand: removed files must be removed from the deployed checkout too.

Verify the result after every deployment:

1. Check GET /api/health.
2. Sign in and load the dashboard.
3. If routing or SSR changed, open an affected workspace page and confirm that it hydrates and works.

The build and test commands cannot detect a browser-only hydration failure. Keep dependencies pinned to their declared versions and review dependency updates as part of a release.