[open-swe] feat: Add Dockerfiles for all microservices #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![open-swe[bot]](https://avatars.githubusercontent.com/in/1395372?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #7
This PR adds Dockerfiles for all four microservices in the repository, enabling containerized deployment of the entire application stack.
Changes Made
java-twitter-feed-api/Dockerfile): Multi-stage build with OpenJDK 8 and Tomcat 8, configured for Twitter OAuth integrationnodejs-users-api/Dockerfile): Node.js 14 Alpine with MongoDB and email service configurationpython-email-api/Dockerfile): Python 3.8 Alpine with Falcon/Gunicorn, Gmail SMTP and MySQL integrationphp-ui/Dockerfile): PHP 7.4 with Apache, serving all frontend assets and configured for backend service communicationAll Dockerfiles follow best practices including layer caching optimization, proper environment variable configuration, and appropriate port exposure for each service.