Deployment

Git push is a remote the provider hands over and needs nothing but git; a connected repo is one they watch on GitHub or GitLab, which is a different workflow with a different failure mode and an account somewhere else. A container image means the unit of deployment is built before the provider ever sees it, file transfer is upload over SFTP or plain FTP — still the normal route on shared hosting, and still the thing that makes a deployment unrepeatable — and a control panel is a button. Most providers offer several, and the one worth filtering on is the one a team would actually use. Two things are deliberately elsewhere: a shell is a way in once code has landed rather than a way of deploying, recorded as shell access, and a CLI or an API belongs to automation.

4 values in use. 67 records do not record this field. For a further 12 the question does not apply, so there is nothing to record.

• GitDeploying means pushing a commit.65 records
• Container imageBuilt before the provider sees it.33 records
• Control panelDeployment as a button.83 records
• File transferUpload, and hope.57 records