app

Manage your applications using the following commands:

runway app create
runway app show
runway app ls
runway app deploy
runway app restart
runway app plan set
runway app rm
runway app route on/off
runway app lockdown on/off

global flags

When working within your app’s repository, we usually guess the app from the git-remote that we created with runway app create. If you work outside of this context, all subcommands of runway app support the following flag:

-a
--app

app create

Examples:

runway app create
runway app create my-app

The app name, if given, must be unique across Runway. If not given, we will chose a random app name.

Creating an application has additional options:

short version	long version	description
`-p`	`--plan`	the plan to use
n/a	`--persistence`	enable persistence
`-r`	`--region`	for available locations see `runway region ls`

Plus options to inherit config settings from other apps, see below.

plans

All plans are available via runway plan ls or on our website.

You can up- or downgrade your app’s plan at any time. See the plan documentation for details.

persistence

By default applications on Runway are using ephemeral disks — each deploy is a brand new environment.

--persistence enables a volume which is mounted at /data. You can use this volume to save data that should be kept across deploys. The caveat is that the volume needs to be released during a deployment, which may cause short blips!

Persistence can be enabled for Scale plans and up. Once enabled, it cannot be disabled.

Worker and init processes do not have access to the /data volume.

inheriting configs from other apps

Running runway app create ... --inherit-from=my-other-app will copy over the config values (env vars) and the settings (routing and lockdown) from another app.

You need at least viewer permissions on the app you want to inherit from. There is also --with-config-from=APP and --with-settings-from=APP to only do one or the other.

app restart

Restarts the app, applying the latest configuration.

If used as app restart --release=$VERSION, it restarts the app as it was at the given version. This can be used to revert back to older configurations and/or builds.