How r1aguilar/oracled2rc works
Project type and purpose
• This is a full-stack, cloud-native Task Manager (“MyTodoList”) application.
• Frontend: React.js SPA living under backend/src/main/frontend.
• Backend: Spring Boot microservice (Java) exposing REST APIs, handling auth (JWT), business logic, persistence.
• Infrastructure as Code: Terraform scripts provisioning OCI resources (API Gateway, Container Engine (OKE), Autonomous DB, Object Storage, etc.).
• Utilities and scripts for CI/CD, cluster setup, container image builds, and database initialization.
File structure
Top-level directories:
– MtdrSpring/backend: Maven-based Spring Boot project, includes Dockerfile, build/deploy scripts, Java source (controller, service, repository, model, security, config), React frontend under src/main/frontend.
– MtdrSpring/terraform: OCI resource definitions for API gateway, Kubernetes cluster, DB, storage, networking.
– MtdrSpring/utils: shell & Python helper scripts for environment setup, destroy, and token management.
– MtdrSpring/*.sh: high-level setup/destroy wrappers.
– test/: sample Dockerfile and Python test script.
Key patterns:
– Monorepo with combined frontend and backend artifacts.
– Spring Boot serves frontend static assets (built React bundle) from /static.
– Terraform defines cloud infra; scripts invoke terraform & OCI-CLI.
README insights
• Emphasizes React frontend + multiple possible backends on OCI Cloud Shell.
• Dependencies: oci-cli, python2.7, terraform, kubectl, maven.
• Shows an ER model for the Autonomous Transaction Processing (ATP) database.