FerryDocs
ReferenceBlueprint spec

Datastores that exist

For a datastore that exists, an apply changes only the resource limits.

Edit on GitHub
ferry.yamlentry app-dbLimitsmemory, CPUOther keysversion, userapp-dbnew limits

New limits in the file go to the container, with no restart.

1 / 2

When a exists, a changes only its . Ferry changes them in place, with no restart.

Keys that do not change it

The keys postgresMajorVersion, databaseName and user apply only when Ferry creates the datastore.

If one of them is different from the datastore that exists, the apply gives this warning and continues:

datastores are not changed in place (ignored)

The same name, the other kind

A file can ask for a Postgres datastore with the name of a Redis datastore that exists, or the opposite. This is a conflict: the apply stops with the status 409.

Redis and Key Value

An entry of services with the type redis or keyvalue creates a Redis datastore, not a service.

Resource limits

A plan, or the keys memoryLimit and cpuLimit, set the memory limit and the CPU limit of each container.

On this page

Keys that do not change itThe same name, the other kind