fix: align ecosystem.config.cjs with actual production pm2 process names
The file previously defined dev-backend-midtrans/dev-frontend-midtrans, but the real production processes are named backend-midtrans-prod and frontend-midtrans-prod (confirmed via pm2 ls on the server) and were started with different serve invocation flags (interpreter: none, -s dist -p 3000 instead of interpreter: serve, -p 3001). This file was previously out of sync with reality, so NODE_ENV=production set here never actually reached the running backend process. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
28ccc8001f
commit
975f26be59
|
|
@ -1,7 +1,7 @@
|
|||
module.exports = {
|
||||
apps : [
|
||||
{
|
||||
name : "dev-backend-midtrans",
|
||||
name : "backend-midtrans-prod",
|
||||
script : "server/index.cjs",
|
||||
|
||||
env: {
|
||||
|
|
@ -9,11 +9,11 @@ module.exports = {
|
|||
}
|
||||
},
|
||||
{
|
||||
name : "dev-frontend-midtrans",
|
||||
interpreter: "serve",
|
||||
script : "dist",
|
||||
args : "-s -p 3001",
|
||||
name : "frontend-midtrans-prod",
|
||||
interpreter: "none",
|
||||
script : "serve",
|
||||
args : "-s dist -p 3000",
|
||||
exec_mode : "fork",
|
||||
}
|
||||
]
|
||||
};
|
||||
};
|
||||
Loading…
Reference in New Issue