Fix PM2 cluster mode and user permission errors
Some checks failed
Cloud Node Container / Build-and-Push (18) (push) Successful in 1m52s
Cloud Node Container / Build-and-Push (22) (push) Has been cancelled
Cloud Node Container / Build-and-Push (20) (push) Has been cancelled

- Force PM2 to use fork mode instead of cluster mode
- Disable wait_ready to avoid startup issues
- Add PM2 ready signal to simple-website server
- Add PM2 status check after startup
- Set NODE_ENV=production for PM2 startup

The cluster mode was causing the UID 1002 error. Fork mode runs
the process directly as the specified user without additional
permission complications.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
2025-07-24 09:53:01 -07:00
parent 205c1c4d68
commit 68ef106277
3 changed files with 15 additions and 2 deletions

View File

@@ -26,4 +26,8 @@ app.get('/ping', (req, res) => {
app.listen(port, () => {
console.log(`Simple website running on port ${port}`);
// Send ready signal to PM2
if (process.send) {
process.send('ready');
}
});