Installation, configuration, sites, databases, previews, automation, and server provisioning organized as a systematic product manual.
Install the CLI, create a first shipper.yml, and run validate, plan, and apply in the intended order.
The core mental model behind Shipper: providers, projects, profiles, and resource lifecycle.
How Shipper thinks about creating, reusing, updating, and destroying provider-managed resources.
Entry point for structuring shipper.yml, with separate reference pages for concepts, providers, projects, profiles, commands, and deployment features.
How the providers block is structured, how projects reference providers, and where provider-specific options belong.
How projects are defined, how repositories and paths are configured, and which settings are shared across profiles.
How deployment environments are modeled, including branch selection, domains, previews, databases, and infrastructure.
How Shipper creates, updates, deploys, and destroys application sites across environments.
How Shipper provisions, reuses, and cleans up servers as part of a deployment profile.
How databases are declared, named, created, linked, and cleaned up across deployment profiles.
How preview environments are named, deployed, and cleaned up for pull requests.
What `shipper validate` checks, when to run it, and how to interpret failures.
What `shipper plan` previews, how to use it safely, and how to read create, reuse, and destroy intent.
What `shipper apply` executes, how it uses the selected profile, and what to verify before running it.
What `shipper destroy` removes, how destroy intent should be reviewed, and where cleanup boundaries come from.
How to wire Shipper into CI workflows for production deploys, preview environments, and cleanup jobs.
How the CLI is packaged, released, and distributed across local installs, binaries, and GitHub Actions.