How eooce/choreo-2go works
Project type and purpose
• The top‐level Dockerfile + GitHub Actions workflow suggests it’s built, tested, and auto-deployed via CI/CD.
File structure
• .github/workflows/auto-deploy.yml → CI/CD pipeline for build + deploy
• Dockerfile → container image definition
• files/
• package.json + index.js → Node.js application root
• config.json → runtime configuration
• server/ → backend API routes & controllers
• switch/ → business-logic module or feature-toggle routing
• web/ → frontend code (static assets or a Single-Page App)
Final advice
• Infrastructure touchpoints (CI/CD, container registry, target runtime).