feat: Docker runtime and CI pipeline for server (#15)#18
Open
suyashkumar102 wants to merge 3 commits intoc2siorg:mainfrom
Open
feat: Docker runtime and CI pipeline for server (#15)#18suyashkumar102 wants to merge 3 commits intoc2siorg:mainfrom
suyashkumar102 wants to merge 3 commits intoc2siorg:mainfrom
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
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.
Closes #15
Added the Dockerfile for the server and the GitHub Actions workflow that builds and pushes the image to GHCR.
The workflow only triggers when files under server/ change, so client-side or unrelated changes don't waste CI minutes. On PRs it just builds to catch any breakage, on merges to main it actually pushes to the registry. Images get tagged with latest, branch name, and commit SHA so you can always trace what's running.
Also threw in a small pytest suite that statically checks the Dockerfile and workflow are configured correctly — catches things like someone accidentally removing the cache config or breaking the push condition.