Get up and running in a few minutes. On this page, you deploy a template, read its connection details and connect your own app to it.
All you need is a Runway account. The examples use MariaDB, but the steps are the same for every template.
You can also deploy templates on the command line.
This example deploys MariaDB and connects an app called my-shop to it.
Install the CLI. See the install docs.
Log in:
runway login
Add an SSH key. See key setup, or use the shortcut:
runway local key setup
Create an app with the suggested plan, then deploy the template to it:
runway app create --app=my-db --plan=start-m-launch
runway app deploy template --app=my-db --template=mariadb \
database_name=shop username=shop
database_name and username are inputs. An input you leave out gets its
default. The page of each template lists its inputs.
DSN or URL only works within Runway, and only from your apps.Show the connection details:
runway app show --app=my-db --reveal
The output contains a DSN (or a URL). Without --reveal, the password is
replaced by the name of the config value that holds it.
Pass the DSN to your app as a config value:
runway app config set --app=my-shop \
DATABASE_URL='mysql://shop:...@...:3306/shop'
runway app restart --app=my-shop
TS_AUTHKEY=tskey-auth-... to the app’s config
and restart it. Click here to learn more about Tailscale on Runway.Not every template is reachable from the internet.
Software without a login, or without encryption on the wire, stays internal: only your apps on Runway can connect to it. This is the case for most databases and caches.
Software that speaks HTTP, and has a web UI or an API you may want to use from outside, is also published on a public HTTPS address. Every request then needs a login, a token or an API key.
The description of each template tells you which one applies.