splashdown

Per-checkout or per-worktree simulators, emulators, and dev ports.

splashdown pins system resources (dev ports, env vars, iOS simulators, Android emulators) to each git checkout and coordinates them machine-wide, so concurrent worktrees of the same (or different) projects never collide.

splashdown demo: two git worktrees automatically get different, non-colliding ports

New here?

Start with Getting started for a web or backend project, or Getting started with mobile for a mobile app. The README has the one-minute quick start.

Getting started¶

Getting started: install, splash init, and your first per-checkout ports.
Getting started with mobile: simulators, emulators, and machine-wide physical devices.

Guides¶

How it works: the git-hook + env-loader glue, and the four files splash manages.
How it compares: splashdown vs Galactic, Worktrunk, VibeChard, and adjacent tools.
The recipe: splashdown.toml: the committed config for apps, resources, and mobile targets.
Per-checkout overrides: add local target variants in splashdown.local.toml.
Settings: behavior toggles and where they live.
Shell completion: bash/zsh tab-completion setup.
Running and managing devices: run/start/stop, auto-upgrade, iOS/Android/physical.
Framework wiring (splash doctor): detect and patch configs that hardcode the port.
Profiles and loaders: how splash init decides what to scaffold.
Monorepos: multi-app workspaces, worked end to end.

Reference¶

CLI reference: every splash subcommand at a glance.
Global port coordination: how the machine-wide registry avoids collisions.
CI integration: the splashdown.env pattern for ephemeral runners.