Merged
Conversation
…kend container to GHCR upon merging to `main`. * **Optimized Dockerfile**: Added `backend/Dockerfile_build_and_publish` using a multi-stage build. * **GitHub Action**: Added `.github/workflows/publish-backend.yml` to automatically build and push the container. * **Versioning**: Images are tagged with `latest` and `sha-<short_commit_hash>`. * **Size & Compatibility**: We use `rust:1.91-slim` (based on Debian Bookworm) for building and `debian:bookworm-slim` for the final runtime. This pairing ensures binary compatibility while stripping out the massive build toolchain (~1GB+) to leave a minimal, production-ready image. * **Separation of Concerns**: Kept the original `Dockerfile` for local development/debug builds, while the new `Dockerfile_build_and_publish` is strictly for deployment artifacts. **Action Required After First Run:** Since this repository is private, the new package will be created as **Private** by default. To make it publicly accessible: 1. Wait for the first Action run to complete successfully. 2. Go to the repository/organization's **Packages** page. 3. Select the `execution-events-example` package. 4. Go to **Package Settings** -> **Change visibility**. 5. Change visibility from **Private** to **Public**.
ghost
requested review from
0xflashboy,
AustinGreen,
Camillebzd,
Im-Madhur-Gupta,
iamvukasin,
marcuspang,
mijovic and
nkrishang
as code owners
|
Deployment failed with the following error: View Documentation: https://vercel.com/docs/accounts/team-members-and-roles |
ghost
changed the title
Im-Madhur-Gupta
pushed a commit
that referenced
this pull request
Jan 14, 2026
* Dockerize backend * This PR introduces an automated workflow to build and publish the backend container to GHCR upon merging to `main`. (#59) * **Optimized Dockerfile**: Added `backend/Dockerfile_build_and_publish` using a multi-stage build. * **GitHub Action**: Added `.github/workflows/publish-backend.yml` to automatically build and push the container. * **Versioning**: Images are tagged with `latest` and `sha-<short_commit_hash>`. * **Size & Compatibility**: We use `rust:1.91-slim` (based on Debian Bookworm) for building and `debian:bookworm-slim` for the final runtime. This pairing ensures binary compatibility while stripping out the massive build toolchain (~1GB+) to leave a minimal, production-ready image. * **Separation of Concerns**: Kept the original `Dockerfile` for local development/debug builds, while the new `Dockerfile_build_and_publish` is strictly for deployment artifacts. **Action Required After First Run:** Since this repository is private, the new package will be created as **Private** by default. To make it publicly accessible: 1. Wait for the first Action run to complete successfully. 2. Go to the repository/organization's **Packages** page. 3. Select the `execution-events-example` package. 4. Go to **Package Settings** -> **Change visibility**. 5. Change visibility from **Private** to **Public**. --------- Co-authored-by: Brandon Graham <brandon@monad.foundation>
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
1 participant
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.
Summary of Changes
This PR introduces an automated workflow to build and publish the backend container to GHCR upon merging to
main.backend/Dockerfile_build_and_publishusing a multi-stage build..github/workflows/publish-backend.ymlto automatically build and push the container.latestandsha-<short_commit_hash>.Reasoning
rust:1.91-slim(based on Debian Bookworm) for building anddebian:bookworm-slimfor the final runtime. This pairing ensures binary compatibility while stripping out the build toolchain to leave a minimal image.Dockerfilefor local development/debug builds, while the newDockerfile_build_and_publishis strictly for production artifacts.Important Next Steps
Action Required After First Run:
Since this repository is private, the new package will be created as Private by default. To make it publicly accessible:
execution-events-examplepackage.