From 73531f38aedd879706f1d1a51b4f0fa18728fe39 Mon Sep 17 00:00:00 2001 From: syntaxbullet Date: Fri, 30 Jan 2026 14:18:45 +0100 Subject: [PATCH] docs: clarify update command behavior in production Docker environment --- shared/modules/admin/update.service.ts | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/shared/modules/admin/update.service.ts b/shared/modules/admin/update.service.ts index 4de2175..de74dc6 100644 --- a/shared/modules/admin/update.service.ts +++ b/shared/modules/admin/update.service.ts @@ -263,11 +263,21 @@ export class UpdateService { /** * Trigger a restart + * + * In production Docker (with restart: unless-stopped), exiting the process + * will cause Docker to restart the container. For a full rebuild with code changes, + * use the deploy.sh script or GitHub Actions CI/CD instead of this command. + * + * Note: The /update command works for hot-reloading in development and minor + * restarts in production, but for production deployments with new code, + * use: `cd ~/Aurora && git pull && docker compose -f docker-compose.prod.yml up -d --build` */ static async triggerRestart(): Promise { if (process.env.RESTART_COMMAND) { + // Custom restart command from environment exec(process.env.RESTART_COMMAND).unref(); } else { + // Exit process - Docker will restart container, dev mode will hot-reload setTimeout(() => process.exit(0), 100); } }