torbo/flyer-crawler.projectium.com
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pm2 worker fixes

Browse Source
This commit is contained in:
Torben Sorensen
2025-12-27 23:29:46 -08:00
parent af5644d17a
commit ddd4ad024e
4 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitea/workflows/deploy-to-prod.yml
View File

@@ -158,7 +158,7 @@ jobs:
else else
echo "Version mismatch (Running: $RUNNING_VERSION -> Deployed: $NEW_VERSION) or app not running. Reloading PM2..." echo "Version mismatch (Running: $RUNNING_VERSION -> Deployed: $NEW_VERSION) or app not running. Reloading PM2..."
fi fi
pm2 startOrReload ecosystem.config.cjs --env production && pm2 save pm2 startOrReload ecosystem.config.cjs --env production --update-env && pm2 save
echo "Production backend server reloaded successfully." echo "Production backend server reloaded successfully."
else else
echo "Version $NEW_VERSION is already running. Skipping PM2 reload." echo "Version $NEW_VERSION is already running. Skipping PM2 reload."

2
.gitea/workflows/deploy-to-test.yml
View File

@@ -406,7 +406,7 @@ jobs:
# Use `startOrReload` with the ecosystem file. This is the standard, idempotent way to deploy. # Use `startOrReload` with the ecosystem file. This is the standard, idempotent way to deploy.
# It will START the process if it's not running, or RELOAD it if it is. # It will START the process if it's not running, or RELOAD it if it is.
# We also add `&& pm2 save` to persist the process list across server reboots. # We also add `&& pm2 save` to persist the process list across server reboots.
pm2 startOrReload ecosystem.config.cjs --env test && pm2 save pm2 startOrReload ecosystem.config.cjs --env test --update-env && pm2 save
echo "Test backend server reloaded successfully." echo "Test backend server reloaded successfully."
# After a successful deployment, update the schema hash in the database. # After a successful deployment, update the schema hash in the database.

2
.gitea/workflows/manual-deploy-major.yml
View File

@@ -157,7 +157,7 @@ jobs:
else else
echo "Version mismatch (Running: $RUNNING_VERSION -> Deployed: $NEW_VERSION) or app not running. Reloading PM2..." echo "Version mismatch (Running: $RUNNING_VERSION -> Deployed: $NEW_VERSION) or app not running. Reloading PM2..."
fi fi
pm2 startOrReload ecosystem.config.cjs --env production && pm2 save pm2 startOrReload ecosystem.config.cjs --env production --update-env && pm2 save
echo "Production backend server reloaded successfully." echo "Production backend server reloaded successfully."
else else
echo "Version $NEW_VERSION is already running. Skipping PM2 reload." echo "Version $NEW_VERSION is already running. Skipping PM2 reload."

12
ecosystem.config.cjs
View File

@@ -3,6 +3,18 @@
// It allows us to define all the settings for our application in one place. // It allows us to define all the settings for our application in one place.
// The .cjs extension is required because the project's package.json has "type": "module". // The .cjs extension is required because the project's package.json has "type": "module".
// --- Environment Variable Validation ---
const requiredSecrets = ['DB_HOST', 'JWT_SECRET', 'GEMINI_API_KEY'];
const missingSecrets = requiredSecrets.filter(key => !process.env[key]);
if (missingSecrets.length > 0) {
console.warn('\n[ecosystem.config.cjs] ⚠️ WARNING: The following environment variables are MISSING in the shell:');
missingSecrets.forEach(key => console.warn(` - ${key}`));
console.warn('[ecosystem.config.cjs] The application may crash if these are required for startup.\n');
} else {
console.log('[ecosystem.config.cjs] ✅ Critical environment variables are present.');
}
module.exports = { module.exports = {
apps: [ apps: [
{ {