Add automatic Mycel production deploys on mycel-host - #455
Merged
Conversation
Mirror Gaia's continuous-deploy pattern with a peer workflow that runs only on the mycel-labeled self-hosted runner and calls deploy/mycel/deploy.sh for tight Mycel/substrate/client path changes — never Gaia's runner or redeploy.sh (ADR 0030). Co-authored-by: Will Schenk <wschenk@gmail.com>
wschenk
marked this pull request as ready for review
September 2, 2026 22:31
Operators install the Actions runner over IAP from a laptop (gh mint the one-hour token; gcloud ssh runs config + systemd), matching Gaia and keeping mycel off the Gaia runner. Co-authored-by: Will Schenk <wschenk@gmail.com>
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.
Summary
Adds continuous deploy for Mycel as a peer of Gaia’s workflow: push to
main(andworkflow_dispatch) on a self-hosted runner labeledmycelruns the existingdeploy/mycel/deploy.sh. Mycel stays off Gaia’s runner and offredeploy.sh(ADR 0030).Changes
.github/workflows/deploy-mycel.yml— cousin ofdeploy-gaia.ymlwith:runs-on: [self-hosted, mycel]mycel-deploy,cancel-in-progress: falsepackages/mycel,apps/mycel-client,packages/substrate,deploy/mycel, workflow file only — no broadpackages/**/ lockfile)MYCEL_ENV_FILE: /opt/umwelten/deploy/mycel/.env(runbook path)workflow_dispatchonly (neverpull_request)deploy/mycel/README.md— continuous-deploy section: when it fires, one-time runner install (--labels mycel), public-repo warning, manualworkflow_dispatchdeploy/mycel/deploy.sh— header no longer says deploys are person-only; points at the new workflowOut of scope (intentional)
deploy/gaia/redeploy.shdeploy/mycel/deploy.shOperator follow-up
One-time: install a GitHub Actions runner on mycel-host with labels
self-hosted, mycel(see updated README). Until that runner exists, the workflow will queue.