docs: clarify update command behavior in production Docker environment
Some checks failed
Deploy to Production / test (push) Failing after 21s
Deploy to Production / build (push) Has been skipped
Deploy to Production / deploy (push) Has been skipped

This commit is contained in:
syntaxbullet
2026-01-30 14:18:45 +01:00
parent 5a6356d271
commit 73531f38ae

View File

@@ -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<void> {
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);
}
}