feat: setting up frontend docker-compose service#96
Merged
Conversation
zowks
approved these changes
May 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Briefly describe what this PR does :
Setting up a docker-compose service for the frontend application
Context / Motivation
Explain why this change is needed:
Ease of deployment and testing
Related Links
Screenshots (if applicable)
Checklist
Additional Notes
I also tool advantage of the PR context to align both backend and frontend Dockerfiles, as well as renaming the hallmaster-postgres service to hallmaster-database, to follow the naming convention (hallmaster-nestjs -> hallmaster-backend, hallmaster-sveltkit -> hallmaster-frontend)