Hi Railway Support,

I'm reporting a critical issue with the Mercury Railway template (repo: 4bade3/mercury-railway).

Problem: The Mercury template deploys successfully but the daemon process runs in the background with no way to monitor or debug it. The container starts, Mercury initializes, but then the process backgrounds itself and becomes inaccessible.

Root Cause: The Dockerfile uses CMD ["mercury", "start"] which backgrounds the Mercury daemon. This breaks Railway's ability to:

Keep the container alive (the main process exits after backgrounding)

Stream logs from the daemon

Monitor the service health

What I've Tried:

Deploying with no custom startCommand (uses default Dockerfile CMD)

Custom startCommand to tail daemon logs

Multiple redeployments

Current State:

Service ID: 799432c1-f8bd-404b-9fde-b1919fd33768

Container starts but Mercury daemon logs are at /root/.mercury/daemon.log (inaccessible)

No Telegram responses received despite correct configuration

Cannot debug because daemon output is not visible

What Needs to Happen: The template needs to be fixed to run Mercury in foreground mode or tail the daemon logs so the container stays alive and logs are visible. The Dockerfile CMD should be changed from ["mercury", "start"] to something that keeps the process in the foreground.

Please advise on next steps or fix the template.