How limjiajing123/portfolio_instance_only works
Project type and purpose
• This is a full-stack personal portfolio web application (“portfolio_instance_only”).
• Frontend: React app (components, assets, CSS, build output) served via Nginx.
• Backend: Node.js service (server.js, Express endpoints, Redis integration, data modules).
• Infrastructure: Docker Compose for local/pre-prod, Terraform + AWS (ECR/ECS) for production.
• CI/CD: GitHub Actions workflows (ci-preprod, deploy).
File structure
• Top-level:
• .github/workflows: CI and deploy pipelines.
• docker-compose.yml/docker-compose.preprod.yml: local and pre-prod multi-container setup.
• terraform-aws/: IaC (provider, ECR registry, ECS cluster/services, task definitions).
• backend/: Node.js service code, Dockerfile, Redis client, mock data, package files.
• frontend/: React source (src/), public assets, built artifacts (build/), Dockerfile, nginx.conf.
• tests/: Python smoke and unit tests for frontend & backend.
• Architectural signals:
• Clear separation of UI (React/Nginx) and API (Node.js).
• Redis as a caching or session store.
• Docker Compose orchestrates three containers (frontend, backend, redis).
• Terraform drives cloud deployment on AWS ECS Fargate, with container tasks and ECR registry.
README
• Minimal content (“portfolio_instance_only”) but file tree reveals tech stack and infra approach.