The deployer interacts with a cloud provider to deploy Airnode programmatically, without requiring you to click through a lot of ever-changing graphical interfaces. For it to do so, a cloud project setup and credentials are required and was discussed in Configuring an Airnode. There is additional guidance in the AWS and GCP quick start tutorials mentioned above.
The deployer image is containerized as a Docker image. This will deploy the Airnode to the cloud provider without the worry of installing dependencies and is the recommended way to do a deployment. If you do not already have docker installed go to the Docker website and install it.
At this point a project should resemble the following. The config.json, secrets.env, aws.env (if deploying to AWS) and gcp.json (if deploying to GCP) files should be ready to go. Other files and folders added to the project are expected and are ignored by the deployer image.
Avoid running multiple deployments simultaneously as doing so might result in a broken deployment. If this occurs, the standard removal approach may not succeed and Manual Removal may be required.
From the root of the project directory run the Docker image command deploy as shown below to deploy the Airnode. When the deployment has completed a receipt.json file will be written to the project directory, which is mounted to the /app/config directory within the container. This file contains important configuration information about the Airnode and is needed to remove the Airnode should the need arise.
Normally (for Linux/Mac/WSL2) the deployer image deploy command is run by the user root. This may cause permission issues when the receipt.json file is generated. Optionally you can specify the UID (user identifier) and GID (group identifier) that the deployer image should use. Do so by setting the environment variables USER_ID and GROUP_ID, otherwise omit the line containing the variables.
The receipt.json file is a product of a deployment attempt. It contains Airnode configuration and deployment information and is used to remove the Airnode. The field success is important in that it specifies whether the deployment was successful or not.