What is Apps?
Apps runs a container image, a compose file, or a repository the platform builds, on machines of your own behind a domain with a certificate.
You find it under Apps in the Deutsche Cloud Console. The platform provisions the machines, pulls your images, checks that the published service answers, and only then moves the domain onto the new version. If anything fails on the way, the version that was serving keeps serving.
When to use it
- You have a container image, from your own registry or a public one, and want it running behind HTTPS without managing a machine.
- You have a docker-compose file with a web service and the things beside it (a database, a worker, a cache).
- You have source code in a repository and want each push built and rolled out.
- You build in CI (GitHub Actions or any other) and want one command that deploys and fails the job when the deployment fails.
Concepts
| Term | Meaning |
|---|---|
| App | One deployable thing with a name, a URL, an environment, and a machine size. |
| Source | Where the app's software comes from: an image already in a registry, a compose file, or a repository the platform builds. |
| Published service | The one container reachable from outside, through the app's domain. For an image app it is the image itself; for a compose app you name it. |
| Deployment | One attempt to put a specific image or compose file live. Each has a generation number; the newest live one is what the domain serves. |
| Machine | The instance the app runs on, one per replica. It appears under Compute as well, in your organization's private network. |
| Default URL | https://<app>.<organization>.apps.platform-development.deutschecloud.app, derived from the names, never stored. |
| Custom domain | A hostname you own, pointed at the app. It gets its own certificate. Inside one of your hosted zones the platform points it itself. |
| Activity | The event stream of a deployment: every provisioning step, written by the machine itself and by the platform. |
| Release command | A command the app runs once per deployment, from the new image, before traffic moves (pnpm db:migrate, for example). |
| Health check | The path, port and expected status that decide when a new container is ready. |
| Binding | A managed database, cache, Kafka cluster, RabbitMQ broker or Document Database attached to the app, from which every rollout generates the connection variables (DATABASE_URL, REDIS_URL, …). |
| Scheduled job | A command run on a cron schedule in the app's image, with its environment, on one of its machines. |
See Apps and sources, Deployments and Compose files for the concepts that need more than a row.
Pricing
Every machine of an app is a compute instance and is billed as one, per started hour; the deployments and custom domains themselves cost nothing. Create app shows the estimate for the machine size and replica count you choose. The machine that builds an image from a repository is a platform machine, not one of your instances: it runs for the build, is deleted once the image is pushed, and is not billed to you.
Interfaces
- Deutsche Cloud Console: Apps, then Create app. Each app has tabs for Deployments, Domains, Scheduled jobs, Environment, Runtime, Logs, Metrics and more.
- CLI:
dcloud deploy …, for exampledcloud deploy apps list.dcloud deploy apps deploystarts a deployment and waits for it, for CI. - API:
/deploy/api, authenticated with a session or an access key. - Terraform:
dcloud_app,dcloud_app_env,dcloud_app_domain,dcloud_app_database_binding,dcloud_app_cache_binding,dcloud_app_errors_binding,dcloud_app_jobanddcloud_app_registry_credentials. Creating andcloud_appdoes not deploy it.