ownstack app

List & info

$ ownstack app list                         # or `ownstack apps`
$ ownstack app info [APP]                   # status, primary domain, deployed SHA per stack

Deploy targets (multi-stack)

$ ownstack app stacks <app>
$ ownstack app stacks:add <app> <stack>
$ ownstack app stacks:remove <app> <stack>

Domains

$ ownstack app domains <app>
$ ownstack app domains:add <app> example.com [--cert=FILE --key=FILE]
$ ownstack app domains:remove <app> <id>

Build & type

$ ownstack app build-type <app> [dockerfile|buildpacks]
$ ownstack app autodeploy <app> [on|off]
$ ownstack app purge-cache <app>
$ ownstack app unlock <app>                  # release a stuck dokku deploy lock

Cloning & replicating

Command	What it does
`ownstack app clone <source> <new>`	Independent copy with its own DB.
`ownstack app replicate <source> <new>`	Shares DB and Redis with the source.

Both accept --stack=NAME, --domain=DOMAIN, --deploy.

Resource limits (memory caps)

$ ownstack app limit <app>
PROCESS              MEMORY          CPU
default              -               -
web                  512m            -
worker               2g              -

$ ownstack app limit <app> --process-type=worker --memory=2g --restart
Set worker memory=2g
Restart triggered for worker.

$ ownstack app limit <app> --process-type=worker --clear

Sets a per-process-type memory cap so a runaway container only kills itself, not the host. See Resource limits for the why and when.

Database link repair

$ ownstack app repair-db postgres <app> [--check-only]
$ ownstack app repair-db mysql <app> [--check-only]

Equivalent to ownstack db repair. --check-only reports without changing anything. See Repair after import.

Local linking

$ ownstack remote -a <app>        # write .ownstack-config in cwd, link to the app
$ ownstack remote                  # show the linked app