wyrd/tools
esc

    ↑↓ Move ↵ Open menagerie results first Search by Pagefind

    menagerie

    Manage workspaces and fleets of development containers through a web UI.

    One container that creates workspaces from Toha templates through their interviews, provisions the Wyrwood binding and Xolotl key a template declares, shows every workspace with its devcontainer, starts, stops, rebuilds, upgrades and deletes them, and backs each one up to its own Git branch. Managers sign in through OpenID Connect; Wyrwood supplies its SSH key and registry credentials.

    Run with Docker

    docker pull ghcr.io/wyrd-company/menagerie:0.4.0
    Read the docs Star on GitHub Other install methods
    Recording of the Menagerie web UI: a template interview creates a workspace, the job console passes issue-key, bind, wait-for-sockets and verify, the row mints a T3 Code token with its text hidden, an upgrade asks one question, and a typed name deletes the workspace.
    Creating a provisioned workspace, minting a T3 Code pairing token, upgrading and deleting. An earlier job built the image, so this create reads the build cache.

    Console tour

    1. The job console of a completed create, with the phases issue-key, bind, create-container, wait-for-sockets, up and verify, and a log line from the template's check that the sockets work.
      02 A create job that provisioned the workspace's credentials.
    2. The Menagerie workspace list with one stopped and two running workspaces, each with its actions, above the list of jobs.
      03 The workspace list with the state of each devcontainer.
    3. The create-workspace form showing a template's interview questions.
      04 A template interview that creates a workspace.
    4. The upgrade form asking only the question the newer template added.
      05 An upgrade that asks one new question.
    5. A workspace row with the time the pairing token ends, a blank block in place of the token, and Copy and Dismiss buttons.
      06 A T3 Code pairing token on its row. This image hides the token's text.
    6. A workspace row with the delete form open, the workspace's name typed and the Delete workspace button enabled.
      07 Delete asks for the workspace's name.

    What it does

    1. Creates a workspace from a Toha template through its interview in the browser. When the template declares what it needs and the host is prepared, the job issues its Xolotl key and makes its Wyrwood binding, so the container has its credentials on its first start, with no step in a CLI or another web interface.

    2. Lists every workspace with the state of its devcontainer, starts, stops and rebuilds it as a job with a live console, and mints a T3 Code pairing token for a running workspace that has the t3code-server Feature.

    3. Upgrades a workspace to a newer template version, asks only the new questions and keeps local edits.

    4. Deletes a workspace after you type its name: backs it up, then removes its binding, Xolotl key, containers and folder. Its backup branch stays.

    5. Backs up each workspace to its own branch in one Git repository after each job that changes it, and can commit and back it up on a schedule.

    6. Runs as one container with no database. Managers sign in through your OpenID Connect provider; Git private keys stay in OpenBao and signing uses Wyrwood.

    Install

    docker pull ghcr.io/wyrd-company/menagerie:0.4.0

    Documentation

    Guide

    Start

    Operate

    Releases

    Latest 0.4.2 Release notes on GitHub

    Fixes

    • An interview of more than one batch of questions moves on from a batch accepted as shown: a re-answered upgrade no longer asks that batch again. The web UI now sends every question it shows, the untouched ones with their defaults, and the template service answers a question a submission leaves out with its default.
    All releases