Skip to main content

SDLC 06: Maintenance and Operations

Revision history: Updated May 2026 — Process management migrated to systemd; simplified branch-to-environment mapping.

1. Environment Management​

BranchEnvironmentDomainPurpose
productionLivepakashop.storeEnd-user production platform
mainStagingstaging.pakashop.storeFinal QA and integration testing

2. systemd Operations​

All backend services are managed by systemd on their respective EC2 hosts.

# Detailed status
systemctl status pakashop-backend.service

# Live log tracking
journalctl -u pakashop-backend.service -f

# Unified status dashboard
./scripts/pakashop-status.sh

3. Incident Response​

3.1 P1 — Critical (Live Platform Down)​

  1. Identify: Check production branch status and EC2 health via CloudWatch/Middleware.io.
  2. Rollback: If caused by a merge, revert the production branch commit.
  3. Notify: alert stakeholders within 15 minutes.

3.2 P2 — High (Staging Down)​

  1. Identify: Check main branch status.
  2. Resolve: Fix the offending code on main or revert if blocking other teams.

4. Scheduled Tasks​

  • Weekly: Check npm audit on main.
  • Monthly: Verify database backups for both Staging and Production stacks.