ConceptsJobs & cron
What a run uses
Each run is a new container that starts from the snapshot of the live deploy.
A run starts. Ferry makes a new container from the snapshot of the live deploy.
1 / 3
A run uses the snapshot of the live deploy. This is true for a one-off job and for a cron job.
What the container gets
| Part | Value |
|---|---|
| Image | The image of the live deploy |
| Variables | The variables of the live deploy, without PORT: a job listens on no port |
| Limits | The memory and CPU limits of the live deploy |
| Network | The private network, with no published port |
| Restart | None |
| Disk | A one-off job gets the disk of the service |
After a change of settings
A change of settings, limits or variables after the live deploy does not apply to a run.
If the job needs the new values, restart the service first.
ferry restart api --follow