pantheon-local/tools

Pantheon work, locally. Without the glue scripts.

Pantheon Local Tools is a free, open-source CLI that makes common Pantheon local-development workflows safer and repeatable across DDEV and Lando — without hard-coding your machine, organization, directory layout, or local stack.

Install Read the docs

MIT licensed · macOS · Linux · Windows via WSL/WSL2

> pantheon-local multidev SITE.ENV --dry-run
> pantheon-local multidev SITE.ENV --provider ddev --start

> pantheon-local pull live --database-only
> pantheon-local status
Why

Keep the workflow. Lose the machine-specific magic.

Pantheon projects tend to accumulate shell aliases, copy-pasted commands, one-off checkout directories, and local-provider assumptions. Pantheon Local Tools puts the repeatable parts behind one CLI while leaving Pantheon, Terminus, DDEV, Lando, Git, and your project configuration in charge of the things they already own.

Provider-neutralUse DDEV or Lando without rewriting the project around the tool.
Configuration-drivenChoose your root, provider, and optional Pantheon Tag routing instead of editing the script.
Fail closedAmbiguous providers, unsafe overrides, and occupied destinations stop instead of guessing.
Workflow

Built around the Pantheon work you actually repeat.

Each command stays narrow: resolve the intent, protect the checkout, delegate to the right upstream tool, and leave useful local state behind.

01 / MULTIDEV

Clone an existing Multidev into an isolated local checkout.

Resolve the authoritative Git URL through Terminus, route the checkout through your configured root or Pantheon Tag mapping, configure DDEV or Lando locally, and refuse to overwrite an existing destination. The command never creates or deletes the remote Multidev.

Multidev behavior → 
> pantheon-local multidev SITE.ENV --dry-run
> pantheon-local multidev SITE.ENV --provider lando --group migration
> pantheon-local multidev SITE.ENV --provider ddev --start

02 / PULL

Refresh the database, files, or both — without pulling code.

Use the provider already associated with the checkout and request only the data you need. Pantheon Local Tools verifies Git HEAD and tracked content before and after the provider pull, then records database and file provenance only after success.

Pull safety contract → 
> pantheon-local pull live
> pantheon-local pull test --database-only
> pantheon-local pull live --files-only

03 / STATUS

Know what this checkout is before you touch it.

Run a local, read-only inspection from the checkout root or any subdirectory. See Pantheon metadata when it is recorded, the detected local provider, Git state, runtime URL when safely available, and independent database/files provenance — without contacting Pantheon or starting the provider.

Status contract → 
> pantheon-local status
> pantheon-local config list
> pantheon-local --version
Providers

DDEV or Lando. Same intent.

The shared Pantheon and Terminus core stays provider-neutral. Provider-specific adapters handle the runtime details while preserving the project's existing .ddev/config.yaml, .lando.yml, services, add-ons, and custom tooling.

DDEVpantheon-local config set provider ddev
Landopantheon-local config set provider lando
Autopantheon-local config unset provider
Provider architecture →
Install

Free to use. Pick the install path that fits your host.

The current stable release is available through Homebrew, a signed Debian/APT repository, downloadable release artifacts, or the portable clone installer.

HomebrewmacOS
brew install zevarix/tap/pantheon-local-tools Tap →
APTDebian · Ubuntu · WSL
curl -fsSL https://raw.githubusercontent.com/zevarix/pantheon-local-tools/main/install-apt.sh | bash Manual setup →

APT stays fingerprint-verified. The bootstrap verifies the canonical public archive fingerprint before installing the dedicated Signed-By keyring/source, then runs normal APT installation. The full manual procedure remains available for users who want to inspect every trust step.

Safety

Useful automation without pretending the local machine is disposable.

The tool is intentionally conservative around code, credentials, provider configuration, and filesystem boundaries.

  • Dry-run before clone.Resolve Pantheon and local routing without creating directories or starting a provider.
  • Git code stays code.Data pulls verify HEAD and tracked content remain unchanged before recording success.
  • No token vault.Terminus and the local providers keep ownership of their supported Pantheon authentication flows.
  • No provider takeover.Local overrides are additive; unsafe changes fail instead of clobbering project configuration.
  • No guessing on ambiguity.Provider selection, checkout paths, and existing destinations must resolve safely or the command stops.
Repository trust

The website and signed APT repository share this endpoint.

This landing page is static. APT reads the signed metadata below directly from GitHub Pages; there is no application server or hidden package backend between the client and the published repository files.

  • InReleaseClear-signed stable repository metadata consumed by APT.
  • Archive keyringPublic OpenPGP keyring. Verify its fingerprint before trusting it.
  • PackagesPackage index for architecture-independent Debian artifacts.