Manage your applications using the following commands:
runway app createrunway app showrunway app lsrunway app deployrunway app restartrunway app plan setrunway app rmWhen 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--appCreating an application has additional options:
| short version | long version | description |
|---|---|---|
-a |
--app |
the name of the new app (unique across runway) |
-p |
--plan |
the plan to use |
| n/a | --persistence |
enable persistence |
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.
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.
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.