How code-and-brain/oclweb2 works
Project type and purpose
• From the README and file‐tree this is “oclweb2” – a ReactJS single‐page application (SPA) called OCL TermBrowser v2.
• Its purpose is to provide a web client for terminology management, consuming external APIs (Open Concept Lab back end) and optional SSO (KeyCloak).
File structure
• Top‐level files:
• Dockerfile, docker-compose.yml/override/sso – container definitions
• nginx/default.conf.template – static assets host & reverse‐proxy rules
• webpack.config.js – build pipeline for React assets
• src/ – all React source (components, services, hooks, assets)
• public/ – static index.html, environment config injection
• .github/workflows/main.yml – CI build/release pipeline
• No “backend” folder – this is strictly a front‐end. APIService.js calls out to external APIs (configured via public/env-config.js and config.json).
• CI/CD files (release_version.sh, GitHub Actions, start-prod.sh) indicate an automated release/deployment flow.
README for additional insights
• Docker Compose sets up:
• SPA container (built from Dockerfile, serves via Nginx)
• Optionally a KeyCloak container for SSO
• Emphasis on CORS/API_URL pointer to external OCL API endpoints
• CI triggers builds, versions, and deploys to staging/production
Detail without over-splitting
• React components/services under a single “React SPA” block.
• Do not list every component file – instead show the high‐level layers (UI, services, utils).
• Essential elements: static asset hosting, API integration, SSO, and CI/CD.