ConceptsDeploys
What starts a deploy
Each deploy records its trigger, the cause that started it.
| Trigger | Cause |
|---|---|
create | You create a service that has a repository or an image. Add --no-deploy to prevent this deploy. |
manual | ferry deploy, or Manual deploy in the dashboard. |
upload | ferry up sends a local folder. |
webhook | A push to the branch, if auto-deploy is on. |
deploy_hook | A request to the deploy hook of the service. |
blueprint | ferry blueprint apply creates the service, or changes its build or deploy settings. |
rollback | ferry rollback, or Roll back to this deploy. |
restart | ferry restart, or Restart service. |
env_change | You save variables with a restart: ferry env set, ferry env unset, or Save & restart. |
What a manual deploy uses
| Source of the service | A manual deploy uses |
|---|---|
| A git repository | The newest commit of the branch, or --commit <sha> |
| A Docker image | The image, which Ferry pulls again |
| An upload | The last upload |
ferry deploy api --clear-cache # build without the Docker cacheThese causes also give the trigger restart:
- A blueprint that changes only variables.
- A new command for a cron job.
A change to a linked env group, saved with a restart, gives the trigger env_change.
create:POST /api/v1/services.manual:POST /api/v1/services/{id}/deploys.webhook: GitHub callsPOST /hooks/github.