FerryDocs
ConceptsServices

Build and deploy settings

Each service keeps its settings. A change applies at the next deploy.

Edit on GitHub
CLIferry updateDashboardSettings pageAPIPATCHSettingschangedNext deploy

You change a setting with the CLI, the dashboard or the API.

1 / 2

The number of instances is the exception: it applies immediately. The API route is PATCH /api/v1/services/{id}.

The settings

SettingCLI API fieldDefault
Repository--reporepo_urlnone
Branch--branchbranchmain
Image--imageimagenone
Runtime--runtimeruntimeauto
Root directory--root-dirroot_dirthe repository root
Dockerfile path--dockerfiledockerfile_pathDockerfile
Build command--build-cmdbuild_commandthe default of the runtime
Start command--start-cmdstart_commandthe default of the runtime, or the command of the image
Publish directory (static sites)--publish-dirpublish_dirdetected
Port--portportdetected
Health check path--healthhealth_check_pathnone: a TCP check
Instances--instancesinstances1
Cron schedule--scheduleschedulerequired for cron jobs
Disk mount path--diskdisk_mount_pathnone
Memory limit (each instance and job run)--memorymemory_limit_mbthe limit of the server, 512 MiB by default
CPU limit (each instance and job run)--cpucpu_limitthe limit of the server, 1 CPU by default
Custom domains--domain (repeatable)custom_domainsnone
Auto-deploy--no-auto-deploy, --auto-deployauto_deployon

Clear a setting

Terminal
ferry update api --start-cmd ""                    # clear a text setting
ferry update api --port 0                          # Ferry detects the port again
ferry update api --memory default --cpu default    # back to the limits of the server

On this page