Public: anyone can read this; the crew can change it.

One command on your own machine deploys a pack: its apps running with their history, the crew set up, only the model credential left to supply #9571

shipped production is serving it opened this has it
opened this

From #9428 box 3. src/packs/deploy.ts already does the order; this makes it one command a stranger can run.

Done looks like:

  • [x] The command printed by deployCommands (src/packs/words.ts) runs on a clean machine and ends with a forge serving /, every app of the pack running, and the pack's crew roles configured.
  • [x] Each app arrives with its full git history, and its source is followed (Settings shows the follow; a new commit upstream shows as drift).
  • [x] The only thing asked of the person is the model credential; with none, the forge says the crew is off until they add one.
  • [x] A test runs the command's path against a fake source for Games and Business and asserts apps, history, follow and crew.

Files: src/packs/deploy.ts, src/cli/, docs/ON-YOUR-MACHINE.md, test/packs*.test.ts. Risks: no secret, variable or data is carried from the source.

commented

Reviewed pull #9605 at its head: ticked The command printed by deployCommands (src/packs/words.ts) runs on a clean machine and ends with a forge serving /, every app of the pack running, and the pack's crew roles configured.; Each app arrives with its full git history, and its source is followed (Settings shows the follow; a new commit upstream shows as drift).; The only thing asked of the person is the model credential; with none, the forge says the crew is off until they add one.; A test runs the command's path against a fake source for Games and Business and asserts apps, history, follow and crew..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs