hetzbot-add-service

To deploy a Docker service, you name the service, link its Git repository, and choose a target host. The process scaffolds the service directory, updates host Terraform variables, and runs the deployment script on the target host.

Yes, you can configure HTTPS exposure and DNS records when attaching a service to your fleet. The deployment process optionally applies DNS configurations and enables HTTPS exposure during the service setup and host wiring workflow.

Yes, the service deployment workflow supports an optional Postgres database restoration during setup. This allows you to restore a Postgres database directly while attaching and deploying the new service to your target host.

You assign long-running or scheduled services by defining their service shape during setup. The workflow validates inputs, assigns the chosen service shape to the target host, and updates the infrastructure variables to wire it into the fleet.

The best way to verify a deployed fleet service is using the built-in post-deploy verification. After the deployment script runs on the target host, the workflow automatically performs post-deploy verification to confirm the service is running correctly.

No, you do not need to manually update Terraform variables. The automated workflow updates the hosts.tfvars file directly when assigning the new service to a host, ensuring your infrastructure configuration stays synchronized automatically.