A template app needs little care. A few things are good to know.
Templates have their own version, apart from the version of the software.
runway app ls and runway app show tell you when a newer version of a
template is available.
To update, deploy the template again with the same inputs:
runway app deploy template --app=my-db --template=mariadb \
database_name=shop username=shop
The software version is often an input (image_tag). Read the description of
the input before you change it: most databases can upgrade, but not downgrade.
Some inputs, like the name of the database, only apply on the first start.
Passwords are generated on the first deployment and stored as config values of the app. Updates do not change them.
Templates scale within the plan. Each template suggests a plan to start with. When your data or traffic grows, move the app to a bigger plan:
runway app plan set --app=my-db --plan=scale-m-launch
You can change the plan at any time. See plans for the details.
Templates run a single instance: no high availability, unless noted.