Skip to main content

Overview

Stops the local running Applad instance for development use, or tears down all infrastructure for a specific environment. When used with --env, it stops containers, removes services, and disconnects adapters by SSHing into the target, cleaning up, and leaving. Important: Does not delete your database or stored files when tearing down environments.

Usage

applad down [--env <environment>]

Options

--env
string
Tears down all infrastructure for a specific environment — stops containers, removes services, disconnects adapters. SSHes into the target, cleans up, and leaves. Use with care in production. Does not delete your database or stored files.

Examples

Stop local instance

applad down
Stops the local running Applad instance for development use.

Tear down staging environment

applad down --env staging
Completely tears down the staging environment infrastructure. Database and files are preserved.

Tear down production environment

applad down --env production
Warning: Use with extreme care. Tears down all production infrastructure while preserving data.

What Gets Removed

When using --env, the following are removed:
  • Running Docker containers
  • Service configurations
  • Adapter connections

What Is Preserved

  • Database contents
  • Stored files
  • Configuration files in your local project

Safety Notes

  • Use --env production with extreme caution
  • Always verify you’re targeting the correct environment
  • This does NOT delete data — only infrastructure
  • You can rebuild the environment by running applad up --env <environment>

Build docs developers (and LLMs) love