How manoloracine/project354 works
Project type and purpose
• This is a Docker-based full-stack application consisting of:
• A Spring Boot Java backend (service name: backend354)
• A React + Vite frontend (service name: frontend354)
• Purpose: Expose REST endpoints (documented via Swagger) that leverage ImageMagick for image processing, and provide a live-reload React UI to call those endpoints.
File structure
Top-level:
• docker-compose.dev.yml – orchestrates both frontend and backend containers
• Backend354/ – Spring Boot project, with Maven wrapper, pom.xml, Dockerfile
└ src/main/java/com/project/backend354/
├ Backend354Application.java (application entry point)
└ TestController.java (example REST controller)
• frontend354/ – Vite-powered React app, with package.json, tsconfig, Dockerfile, docker-compose.dev.yml
Notable patterns and files:
• Separate Dockerfiles in each service directory
• Swagger UI auto-configuration via Springdoc (implied by README swagger-ui link)
• Live-reload support in the frontend container
• ImageMagick installed inside the backend container
README for additional insights
• docker-compose.dev.yml brings up both services together
• Swagger UI on port 8080 for backend API testing
• React UI on port 5173 with hot-reload
• Backend container bundles ImageMagick for on-the-fly image operations