cloud-node-container

4 Commits

Include renames

Author	SHA1	Message	Date
shadowdao	566cdb5276	fix generate-ecosystem-config.sh Cloud Node Container / Build-and-Push (18) (push) Successful in 1m58s Details Cloud Node Container / Build-and-Push (20) (push) Successful in 1m56s Details Cloud Node Container / Build-and-Push (22) (push) Successful in 1m55s Details	2025-07-31 12:08:07 -07:00
shadowdaoandClaude	a9dd0573ca	Fix PM2 UID type error by using login shell and explicit undefined Cloud Node Container / Build-and-Push (18) (push) Successful in 1m47s Details Cloud Node Container / Build-and-Push (20) (push) Successful in 1m52s Details Cloud Node Container / Build-and-Push (22) (push) Successful in 2m0s Details - Use su with login shell (-) to ensure clean environment - Explicitly set uid/gid to undefined in ecosystem config - This prevents PM2 from trying to parse string UID as integer The error occurred because PM2 was receiving '1002' as a string instead of an integer. By using a login shell and explicitly setting uid/gid to undefined, PM2 won't try to switch users. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-24 10:02:17 -07:00
shadowdaoandClaude	68ef106277	Fix PM2 cluster mode and user permission errors Cloud Node Container / Build-and-Push (18) (push) Successful in 1m52s Details Cloud Node Container / Build-and-Push (22) (push) Has been cancelled Details Cloud Node Container / Build-and-Push (20) (push) Has been cancelled Details - 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>	2025-07-24 09:53:01 -07:00
shadowdaoandClaude	9f0aa4b8b1	Implement auto-generation of ecosystem.config.js and improve container setup Cloud Node Container / Build-and-Push (18) (push) Failing after 38s Details Cloud Node Container / Build-and-Push (20) (push) Failing after 33s Details Cloud Node Container / Build-and-Push (22) (push) Failing after 33s Details - Add automatic ecosystem.config.js generation from package.json - Create app directory automatically if missing - Copy simple-website example when app directory is empty - Remove redundant default app files from configs/ - Add HAProxy support with proper real IP forwarding - Configure nginx to trust proxy headers from private networks - Simplify entrypoint logic - always use /home/$user/app This makes the container more user-friendly by eliminating the need for manual PM2 configuration and ensuring the server always has a working app. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-24 09:01:08 -07:00