feat: [CI] Setup Docker Build & Push Pipeline for Microservices #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📌 Description
This PR implements the Continuous Integration (CI) pipeline requested in #41 to automate the containerization of the MicroForge application.
What does this PR do?
Dockerfile: Created a comprehensive Multi-Stage Dockerfile that defines build targets for all 5 microservices (auth,frontend,login,metadata,notification)..github/workflows/docker-publish.ymlusing a Matrix Strategy. This allows all 5 services to be built and pushed in parallel jobs.v1.0.0),latest, and the Git commit SHA for traceability.Why is this change needed?
Previously, builds and pushes were manual. This automation ensures that every change to the
masterbranch is automatically verified, built, and deployed to the Docker Registry without human intervention.🔗 Related Issue
Fixes #41
🛠️ Type of Change
Please mark the relevant option:
🧪 How Was This Tested?
Describe how you verified your changes:
📸 Screenshots (if applicable)
No UI changes. Workflow logs confirm successful parallel builds:

✅ Checklist
Please confirm the following:
📝 Additional Notes
For this pipeline to function correctly after merging, the project admin must add the following Repository Secrets in
Settings > Secrets and variables > Actions:DOCKER_USERNAME: The Docker Hub username.DOCKER_PASSWORD: The Docker Hub password (or Access Token).