Checklists /Replit /Monitoring
Medium
Read the deployment logs after you publish
The editor console is not the published app. Replit keeps deployment logs for the running process. Look at them after publish, and again after the first users, or you will miss crashes that happen when the workspace is closed.
How to check
- Open the published app's logs.
- Load the public URL and confirm a request or a startup line appears.
- If the process restarts in a loop, read the error before you change random code.
- Confirm secrets are not printed in those logs.
Prompt
Fix prompt
You are working in this repository. Do not add features. Goal: startup and request failures log a single JSON line, and secrets are not included. Steps: 1. Log when the server starts, including the port, not the secrets. 2. On an unhandled error, log the message and stack on the server, and return a short public error. 3. Remove any console.log of env objects. 4. Tell me where those lines will appear once the app is published.