Skip to content

feat(deploy): production-hardening for Render deploy - #3

Merged
KRISHNA-24BCS127 merged 1 commit into
basant-gautam:mainfrom
KRISHNA-24BCS127:main
Sep 4, 2026
Merged

feat(deploy): production-hardening for Render deploy#3
KRISHNA-24BCS127 merged 1 commit into
basant-gautam:mainfrom
KRISHNA-24BCS127:main

Conversation

@KRISHNA-24BCS127

Copy link
Copy Markdown
Collaborator

Summary

Production/deployment hardening for Teamup.

Changes

  • Serve static frontend from public/ only (never repo root) — prevents exposure of .env, source, and credentials that express.static(__dirname) previously leaked.
  • Express hardening: disable X-Powered-By, add security headers, restrict CORS via CORS_ORIGIN.
  • Deploy assets: add Procfile and render.yaml (Render blueprint with health check /api/health).
  • Config: .gitignore now ignores all *.env except .env.example; document deployment in README.
  • CI fix: update syntax-check paths for files moved into public/.

Validation

  • Server boots and connects to MongoDB
  • /, /login, /signup, /dashboard + static assets return 200
  • All 7 CI syntax checks pass locally

- Serve static frontend from public/ only (never repo root; protects .env and source)

- Harden Express: disable X-Powered-By, add security headers, restrict CORS via CORS_ORIGIN

- Add Procfile and render.yaml for Render/Heroku-style deploys + health check route

- Document deploy steps in README; ignore all *.env except .env.example template

- Fix CI syntax-check paths for files moved into public/
@KRISHNA-24BCS127
KRISHNA-24BCS127 merged commit 00ff8f5 into basant-gautam:main Sep 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant