GuidesMigrate from Render
Apply the file again
You can change the file and apply it again. Ferry updates what changed and deletes nothing.
The result lists each resource as create, update or unchanged. Ferry deletes nothing: a resource that you remove from the file stays on the server.
What Ferry does for each change
| Change in the file | Ferry |
|---|---|
| Build or deploy settings of a service | Deploys the service again. |
Only the limits (plan, memoryLimit, cpuLimit) or the variables of a service | Restarts the service, if it is live. Ferry builds nothing. |
No plan, memoryLimit or cpuLimit in the file | Keeps the limits, like numInstances. |
| Version, database name or user of a datastore | Keeps the old values and shows a warning. |
| Limits of a datastore | Changes them in place, without a restart. |
Preview first
ferry blueprint apply render.yaml --dry-runThe dry run shows all these changes and changes nothing. It also shows limit changes, such as memory_limit: 512 MiB → 2 GiB.
The file sets no limit. Then the changes that you made with ferry update --memory or in the dashboard stay.
The blueprint reference describes each key, and how to use the ferry.yaml of Ferry.