CDN.com.tr Help

Publish an application on Platforms

Use CDN Hosting/Platforms to publish WordPress, PHP, or Managed Container workloads through account, package entitlement, platform settings, deploy/status/logs, and delivery method verification.

Back to Help Center Back to section

Getting started

Publish an application on Platforms

Use CDN Hosting/Platforms to publish WordPress, PHP, or Managed Container workloads through account, package entitlement, platform settings, deploy/status/logs, and delivery method verification.

Where to go after the platform flow

After a platform deploy, users usually need to revisit delivery method, DNS/SSL, and operation results.

Domain model

Which domain should serve platform output?

Compare default endpoint for preview, CNAME for production, or Full DNS when root DNS belongs on CDN.com.tr.

CDN Hosting/Platforms Default / CNAME / Full DNS
Open choice guide
Deploy result

Apply Changes and watch Operations

Verify that platform source or Host header changes reached traffic config.

CDN Hosting/Platforms All delivery methods
Open apply guide

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Add Your Website
  4. Content Source: CDN Hosting
  5. Package / entitlement
  6. Hosting/Platforms
  7. Platform app create/deploy
  8. Operations
  9. Delivery hostname / SSL

Prerequisites

  • A package or entitlement that covers the selected platform is purchased in the panel and assigned to the account.
  • The Host header behavior is known for WordPress, PHP, or Managed Container.
  • AI and Knight Online keep their own public host binding behavior.
  • Container deploys need image, registry credentials, secrets, and port data ready.

Decision model

Platform type

When runtime runs on CDN.com.tr, the flow moves away from Pull or Push file setup.

  • WordPress/PHP: platform hosting and app settings.
  • Managed Container: image, deploy, logs, health, and optional object storage.
  • AI and Knight Online: platform-specific public host binding and management flows.

Host header contract

WordPress, PHP, and Managed Container origin Host header behavior is managed here.

  • When Keep request header is selected, the backend sees the incoming public host.
  • When not selected, a fixed host value is sent.
  • AI and Knight Online keep their platform-specific host binding behavior.

Step-by-step guide

1

Prepare account, package, and entitlement

Platform actions may require package capacity and entitlement; purchase is completed in the panel.

  • Select the account in CDN Accounts.
  • Buy and assign the required platform package in the panel.
  • Confirm create or deploy actions do not start without entitlement.

Expected result: Hosting/Platforms can show platform actions for the selected account.

cdnctl equivalent 
cdnctl accounts list
cdnctl packages list --owned --format table
export ACCOUNT_UUID=<account_uuid>
export PAID_PACKAGE_ID=<listed_package_id>
2

Choose CDN Hosting/Platforms as the source

The CDN Hosting selection in the wizard prepares the platform runtime account shell.

  • Choose CDN Hosting in Content Source.
  • Complete the delivery method after the package step.
  • Move to Hosting/Platforms after the account exists.

Expected result: The platform source type is saved on the account and the platform surface is active.

cdnctl equivalent 
cdnctl cdn accounts create --source hosting --delivery custom-subdomain --package "$PAID_PACKAGE_ID" --alias platform-app-demo
export ACCOUNT_UUID=<account_uuid>
3

Set platform type and Host header behavior

Hosting/Platforms shows platform services and the Host header decision together.

  • Select the platform type.
  • Set Keep the request header according to backend expectation for WordPress/PHP/Managed Container.
  • Save or Activate the setting.

Expected result: Platform type and Host header config are stored on the selected account.

cdnctl equivalent 
cdnctl platforms types list
cdnctl platforms type set --account "$ACCOUNT_UUID" --type managed-container
cdnctl platforms origin-host set --account "$ACCOUNT_UUID" --host app.example.com --keep-request-host false
4

Create or deploy the app

Managed Container and similar platforms manage image, port, env/secrets, and health from customer-facing surfaces.

  • Follow the app create/deploy checklist in the platform guide.
  • Check logs, status, and diagnostics.
  • Customer flows must not require SSH, kubectl, or manual DB operations.

Expected result: Operations and platform status surfaces show the deploy result.

cdnctl equivalent 
cdnctl container apps deploy --account "$ACCOUNT_UUID" --name web --image registry.example.com/acme/web:latest --port 8080
cdnctl container apps logs --account "$ACCOUNT_UUID" --app web --tail 100
cdnctl container apps status --account "$ACCOUNT_UUID" --app web
5

Verify publish and operation result

Platform output is also served through default endpoint, full DNS, or custom subdomain.

  • Check delivery hostname and SSL status.
  • Run Apply Changes when needed.
  • Watch success in Operations.
  • Check the application health endpoint publicly.

Expected result: The platform application responds through a customer-facing domain.

cdnctl equivalent 
cdnctl cdn accounts apply --account "$ACCOUNT_UUID"
cdnctl operations list --account "$ACCOUNT_UUID" --latest
curl -I https://app.example.com/health

Verification

  • Package entitlement allows the selected platform.
  • Platform type appears in Hosting/Platforms.
  • Host header behavior and platform exceptions are documented.
  • Deploy/status/logs are available from customer-facing surfaces.
  • Public domain verification happens after Apply Changes and Operations.

Use cases

A customer wants CDN.com.tr to run the application runtime and serve it through a public domain, not only proxy an origin or host static files.

Quick workflow

  1. Account and entitled package are ready.
  2. Choose CDN Hosting/Platforms as the source in the wizard.
  3. Configure platform type and origin Host header in Hosting/Platforms.
  4. Create or deploy the platform app.
  5. Watch Operations, logs, and status.
  6. Verify delivery through Default Endpoint, Full DNS Transfer, or Custom Subdomain.

Checks

  • Platform work is not started without entitlement.
  • AI and Knight Online host binding exceptions remain explicit.
  • Customer guides must not request SSH, kubectl, artisan, or manual DB work.
  • cdnctl capability gaps are documented as product gaps when present.