Switch to Superset

Overview

If your repository already has a setup file from another tool, Superset can turn it into project lifecycle scripts in one click.

Superset looks for these files in the project's root checkout:

Import a setup

When a project has no Superset scripts yet and one of these files exists, the sidebar shows Found Conductor setup (or the tool it found). Click Import.

You can also import at any time from Project settings → Project lifecycle scripts: an Import from Conductor button (or Import from another tool, when there are several) shows while the import would change something.

The import dialog shows, before anything is written:

• The setup, teardown, and run commands Superset will write
• Your current commands, for any field the import replaces
• Every setting that is not imported, and why

If the repository has files from more than one tool, pick the tool at the top of the dialog. The import writes .superset/config.json (and .superset/<key>.sh for long scripts, see below). Commit .superset/ to share it with your team.

What maps where

Orca shared and copied paths. Each worktree.sharedDirectories entry becomes a symlink to the root checkout, and each .worktreeinclude line becomes a copy. Both run before your setup script, and both skip a path that is missing in the root checkout or already present in the workspace. Paths must be literal and relative; globs and .. are skipped. A symlink is not a directory to Git, so ignore a shared directory without a trailing slash (.cache, not .cache/), or it shows up as an untracked file.

cmux setup command. cmux has no setup hook, so Superset picks the first command named setup, project setup, workspace setup, or repository setup. Failing that, it picks a command with the keyword setup, init, initialize, or install whose name or command mentions "setup".

Long scripts

Superset runs each setup, teardown, and run entry in order, joined with &&. A script whose lines can run that way (one complete command per line) is imported as one entry per line, and comment lines are dropped.

A script with shell blocks (if/fi, loops, functions, line continuations, heredocs, or inline comments) is saved to .superset/setup.sh, .superset/teardown.sh, or .superset/run.sh instead, and the config runs it:

{ "setup": ["bash \"$SUPERSET_ROOT_PATH/.superset/setup.sh\""] }

The script runs with bash and set -e, so it stops at the first failed command, as the && chain does. If a later import replaces it with plain commands, the dialog says so and the import deletes the file it wrote.

Environment variables

The import rewrites the other tool's variables to Superset's. Both $VAR and ${VAR} forms are rewritten.

Any other variable from these tools, such as CONDUCTOR_PORT, is kept as written and listed under Not imported. Replace it by hand before you run the script.

Not imported

These settings have no Superset equivalent. The dialog lists each one it finds.

Files larger than 256 KiB, and single fields larger than 64 KiB, are skipped.