open-notebook/supervisord.conf
LUIS NOVO 50157c3c79 fix: use standalone server for Next.js in Docker
Replace 'next start' with 'node server.js' to properly utilize
Next.js standalone output mode in Docker deployments.

Changes:
- Update supervisord.conf to run standalone server
- Update supervisord.single.conf to run standalone server
- Update package.json start script for consistency

This eliminates the startup warning and follows Next.js best
practices for optimized Docker deployments.
2026-01-14 22:03:15 -03:00

40 lines
960 B
Text

[supervisord]
nodaemon=true
logfile=/dev/stdout
logfile_maxbytes=0
pidfile=/tmp/supervisord.pid
[program:api]
command=uv run --no-sync uvicorn api.main:app --host 0.0.0.0 --port 5055
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
autorestart=true
priority=10
autostart=true
[program:worker]
command=uv run --no-sync surreal-commands-worker --import-modules commands
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
autorestart=true
priority=20
autostart=true
startsecs=3
[program:frontend]
command=bash -c "/app/scripts/wait-for-api.sh && node server.js"
directory=/app/frontend
environment=NODE_ENV="production",PORT="8502"
passenv=API_URL,NEXT_PUBLIC_API_URL,INTERNAL_API_URL
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
autorestart=true
priority=30
autostart=true
startsecs=10