Repository navigation
feat(hub): add production runtime and locked setup - #172
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because there is no eligible user to bill.
An enterprise owner can allow the organization to be billed for reviews like this by enabling Copilot code review for users without a license.
alliscode
force-pushed
the
copilot/hub-production-runtime
branch
2 times, most recently
from
November 3, 2026 16:59
dfbfe02 to
9d5f5b1
Compare
Run the built frontend, API, and workers in one image. Keep schema and schedule setup in a separately locked operational script. Co-authored-by: Ben Thomas <25218250+alliscode@users.noreply.github.com> Co-authored-by: Nishiki <1121087+nshki@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Match function directories and call the application Hub consistently. Co-authored-by: Ben Thomas <25218250+alliscode@users.noreply.github.com> Co-authored-by: Nishiki <1121087+nshki@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot
AI
force-pushed
the
copilot/hub-production-runtime
branch
from
November 3, 2026 17:28
9d5f5b1 to
2661da1
Compare
alliscode
requested changes
Nov 3, 2026
alliscode
left a comment
alliscode
left a comment
Collaborator
There was a problem hiding this comment.
I found two issues that can allow setup work to overlap or report the service ready while a worker is unavailable. Please address the inline comments.
Co-authored-by: Ben Thomas <25218250+alliscode@users.noreply.github.com> Co-authored-by: Nishiki <1121087+nshki@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nshki
approved these changes
Nov 3, 2026
alliscode
approved these changes
Nov 3, 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
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.
Why
Operators need a deployable Hub without running migrations in each application process. This is the first layer of #171, targeting
build/hub/new.What changes
A non-root image serves the built frontend and API and runs both existing workers, with shared readiness and shutdown. Individual roles remain available.
Operational scripts live under
hub/server/scripts/. Release setup holds a database advisory lock across Prisma migrations, job migrations, and schedule registration. The deployment orchestrator owns full release serialization and must confirm prior setup has stopped before retrying after failure; the advisory lock cannot protect against connection loss. Worker readiness confirms initialization, not continuous consumer health, while PostgreSQL is checked live.Normal Hub startup never invokes setup. The devcontainer stays unchanged; this does not add a supported local-production installation or product features.
Created from a Slack conversation with @alliscode.