You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Dockerfile for the board server isn't published anywhere, it's just expecting people to come along, build, and self serve. I think building and publishing it to a public registry would be the lowest-friction way to get folks to start using it.
I'm proposing that we set up a fairly simple GitHub actions workflow that builds this image and publishes to the GitHub registry. Most likely this will involve configuring a repo secret to allow I/O with GHCR.io.
The text was updated successfully, but these errors were encountered:
…uilds (#2961)
Fixes#2948
- Builds containers for sqlite and firestore flavoured versions of the
board server
- Tags with sha, short hash, board server semver and latest
- Publishes to: (may want to modify these to some existing google org
repo?)
- ghcr.io/breadboard-ai/board-server-sqlite
- ghcr.io/breadboard-ai/board-server-firestore
- Generates attestations for the containers and also publishes these to
ghcr
The Dockerfile for the board server isn't published anywhere, it's just expecting people to come along, build, and self serve. I think building and publishing it to a public registry would be the lowest-friction way to get folks to start using it.
I'm proposing that we set up a fairly simple GitHub actions workflow that builds this image and publishes to the GitHub registry. Most likely this will involve configuring a repo secret to allow I/O with GHCR.io.
The text was updated successfully, but these errors were encountered: