valentyn-vb / valentyn-vb/Recap-Project-6
Containerize app and add CI workflow
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Companion - Containerize and add CI
Apply DevOps practices to the Spring Boot + Vue monorepo.
Tasks
- Propose a plan for containerizing the app (single image vs. separate frontend/backend images) before implementing anything.
- Once the approach is agreed, write the Dockerfile(s) and confirm the app can be built and run in Docker.
- Add a GitHub Actions workflow that runs on every push: installs dependencies and runs tests for both backend and frontend.
- Make sure Docker build and CI steps correctly reference each part of the monorepo (frontend/backend paths).
Acceptance criteria
- A short plan/proposal exists and is reviewed before implementation starts.
- The app can be built and run via Docker, serving both the UI and the API.
- No secrets/credentials hardcoded — config via env vars.
- CI fails if either the backend or frontend test suite fails.
- CI run passes on a clean checkout with no dependency on local machine state.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by proposing and getting agreement on single versus separate images for the frontend/backend monorepo, then define the Dockerfile(s) and GitHub Actions workflow around the stated frontend/backend paths. Done means Docker builds and serves the UI and API, CI runs both test suites on every push, and the clean-checkout workflow uses environment variables rather than hardcoded secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, java, spring-boot
- Domain
- backend, ci-cd, devops, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100