app config

Configuration settings on Runway are available via environment variables on both builds and running app container(s) alike. This allows you to follow 12-factor principles while running and developing applications.

Encryption

Configuration variables and their values are encrypted at rest, ensuring data security. In transit, all communications with Runway’s API are protected by TLS/SSL.

Commands

The available commands:

runway app config ls: show current configuration
runway app config set: add/update configuration
runway app config rm: remove configuration
runway app config import: import configuration

Your app

Configuration changes are not applied to the running app directly.

After runway config set/rm, run runway app restart to restart the latest app build with the new config values.

Alternatively, do another runway app deploy, for a complete re-build and deployment.

Examples

The following example updates a variable called PORT:

runway app config set PORT=8080

After deploying your application, you will be able to access the variable in the environment. For more details, please see our example apps.

Import

Easily import or bulk-update your app’s configuration from a local .env or .direnv file using:

runway app config import /path/to/file/.env

This ensures seamless integration and keeps your environment variables in sync with Runway.

Tip: Running this in CI?

Add -y (or: --noninteractive, RUNWAY_NONINTERACTIVE=1) to skip confirmation prompts and ensure smooth execution.

Company