لديك ملف Docker Compose؟ مشروعك يصبح مباشرًا خلال ثوانٍ — بأمر واحد على cdn.com.tr. شاهد كيف

CDN.com.tr Help

Choose a managed platform

Pick WordPress, PHP, AI, Knight Online, or Managed Container based on the workload.

Platforms and managed add-ons

Choose a managed platform

Pick WordPress, PHP, AI, Knight Online, or Managed Container based on the workload.

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Hosting / Platforms
  4. Managed platform overview

Prerequisites

  • A package with platform entitlement must be assigned to the account.
  • Platform type is saved for the selected account.
  • Real account/domain data is redacted in screenshots.

Step-by-step guide

1

Open Hosting/Platforms

The platform overview shows WordPress, PHP, AI, Knight Online, and Managed Container choices.

  • Click the platform/hosting icon from CDN Accounts.
  • Read platform type and preflight messages.

Expected result: Platform options and entitlement warnings are visible.

cdnctl equivalent 
cdnctl accounts list
cdnctl container apps list --account <account_uuid>
2

Choose the right runtime type

Simple PHP/WordPress and container workloads use different flows.

  • Choose workload type.
  • Return to package/entitlement step if preflight warns.

Expected result: The user lands on the correct platform guide.

cdnctl equivalent 
cdnctl container apps diagnose --account <account_uuid> --app <app_uuid>

Verification

  • Platform type and entitlement are customer-visible.
  • kubectl/SSH is not documented as a customer step.
  • Missing package state links the user back to billing.

Use cases

A customer is deciding whether an app should be a simple PHP runtime or a containerized deployment.

Quick workflow

  1. Open Platforms.
  2. Review available platform cards.
  3. Select type.
  4. Read preflight warnings.
  5. Continue with the matching guide.

Checks

  • Platform type is saved.
  • Preflight warnings are shown.
  • Unsupported actions are disabled or explained.

Related pages

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.