Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how

CDN.com.tr Help

Platforms and managed add-ons

Use this section for application hosting workflows and managed platform resources.

Platforms and managed add-ons

This section is about running your application on CDN.com.tr’s managed platforms — WordPress, PHP, container apps, and managed add-ons like databases, Redis and object storage — instead of maintaining your own servers. You bring the app; the platform runs, secures and scales it.

Managed Container Apps run your containers on Kubernetes underneath without you operating a cluster: you create an app from an image, set env and secrets, add persistent storage, schedule jobs, and deploy. Managed WordPress and PHP give you a tuned runtime with caching and SSL built in, and add-ons like Redis, a database or an Object Storage bucket attach to your app in a few steps.

You can move an existing app in with no downtime — run your origin on Platforms while your live site keeps serving from the Pull CDN, then switch over when it is ready. Object Storage is S3-compatible, so you can verify it with the standard AWS CLI.

Use cases

  • A Kubernetes app is migrated into Managed Container Apps.
  • A WordPress site needs Redis/database provisioning.
  • A container app needs an Object Storage bucket and AWS CLI verification.

Workflow

  1. Select account.
  2. Choose Hosting/Platforms.
  3. Run preflight.
  4. Create/update resource.
  5. Deploy and watch logs/status.

Checks

  • Platform type is selected.
  • Entitlement and package limits allow the action.
  • Operations/logs show the async result.

Topics

Object Storage and AWS CLI

Create buckets, rotate access keys, bind buckets to apps, and verify with the S3-compatible endpoint.

What you can run — capabilities and limits

A managed container platform (Kubernetes underneath), not a VM or shell server: you bring container images or a docker-compose.yml and the platform runs them, with managed Redis/PostgreSQL/MySQL/NATS add-ons, persistent volumes, internal service DNS, and HTTP(S) exposure through the CDN edge.

Persistent storage for a managed app

Give a container app a persistent volume so its data survives restarts and redeploys: enable storage, set the in-container mount path and size. One volume per app, mounted at one path, on CephFS.

Move a live Pull-CDN site to Platforms with no downtime

Run your origin services on cdn.com.tr Platforms while your site keeps serving via Pull CDN: enable apps alongside your current delivery, build and validate everything on ca-* subdomains, then cut the main domain over only when ready — fully reversible.

Related pages