sase.tr/.changeset/remove-pm2-sase-web.md at ac78816753a08dfced6344e41500dafdc0ffe754

Files

Sync dev → Gitea / Mirror dev to Gitea (push) Has been cancelled

Details

feat(FN-317): remove legacy sase-web PM2 entry (+1 more)

Commits merged:
- docs(FN-317): complete Step 3 — update docs and memory for sase-web removal
- feat(FN-317): complete Step 1 — remove legacy sase-web PM2 entry

Files changed:
.changeset/remove-pm2-sase-web.md |  9 +++++++++
 .fusion/memory/MEMORY.md          |  2 +-
 CLAUDE.md                         |  2 +-
 docs/INDEX.md                     |  8 +++-----
 ecosystem.config.js               | 16 ----------------
 knowledge.md                      |  3 +--
 6 files changed, 15 insertions(+), 25 deletions(-)

Fusion-Task-Id: FN-317

2026-05-13 12:06:08 +00:00

738 B

Raw Blame History

sase

sase
patch

Removed: sase-web entry from ecosystem.config.js

Production web traffic is served via nginx static files from apps/web/dist/ (configured in docker/nginx/sites/sase.tr.conf). The PM2 pnpm dev process on port 3000 was a legacy artifact with NODE_ENV=development — it was never in the production serving path. Current production deployment is Coolify-driven (Docker Compose), which builds a single image serving both API (port 4000) and static frontend assets via nginx.

Rationale: Reduce PM2 process footprint, eliminate confusion about which process serves production traffic, and remove a long-running NODE_ENV=development process that consumed resources without serving any user traffic.

738 B Raw Blame History

738 B

Raw Blame History