Repository navigation
Launch one rig spec as several named teams (rig up <spec> --name <instance>)
#1647
Replies: 2 comments 7 replies
|
Follow-up: before asking, I checked whether something existing already covers this. |
|
Thanks, @klueless-io, for the clear write-up, and for checking the existing routes before asking. Your reading of today's behaviour matches what we see on We've passed this to the team to look into. |
Uh oh!
There was an error while loading. Please reload this page.
What I'm trying to do
I keep one rig spec as a reusable team: a lead, six desks and a reviewer that walk a codebase through a ladder of static-analysis gates, one gate per PR. I point the same spec at different projects with
rig up <spec> --cwd <project>, and sometimes two projects run at once on two machines (one project per machine).What stops me
Every launch takes its name from the spec's
name:field, so every team is calledspaghettiand every seat has the same address (orch-lead@spaghetti,gates-foundation@spaghetti, …) whichever project it is working on. On one machine I can't run a second project without the second launch landing on the first team's name. Across machines the names collide in anything that shows both: dashboards, logs, recordings. Today I keep a copy of the spec per project that differs only inname:, which drifts.What would help
A launch-time name:
rig up <spec> --name spaghetti-appystack --cwd <project>. Seats become…@spaghetti-appystack; the spec stays generic.The part I can't judge from outside
The name is also what
rig up <name> --existing, snapshots and lookups use, so a launch-time name would need to be stored with the rig and kept on restore, not just passed at launch. Happy to help with a PR if this direction is welcome.Evidence:
@openrig/cli0.6.13 (9eeb2e42), macOS.rig up --helplists--plan,--cwd,--env,--existing,--fresh,--preset, but no name option;docs/reference/rig-spec.mddocumentsnameas "Used in session naming ({pod}-{member}@{name}), snapshot identification, and spec library lookup."All reactions