CDN.com.tr Help

Choose content source and delivery method

First decide where the content comes from, then decide which public domain model serves it; this split applies to Pull, Push, and Hosting/Platforms.

Back to Help Center Back to section

Getting started

Choose content source and delivery method

First decide where the content comes from, then decide which public domain model serves it; this split applies to Pull, Push, and Hosting/Platforms.

Continue based on your choice

This page is for deciding; implementation continues in the matching case page.

I chose Pull

Publish an existing website through CDN

Follow origin, Host header, hostname, DNS, SSL, and Apply Changes steps.

Pull CDN Default / CNAME / Full DNS
Open Pull CDN flow
I chose Push + Default

Host static content with Simple Transfer

Upload the file and read it from the default CDN.com.tr endpoint.

Push CDN Default Endpoint
Open Simple Transfer flow
I chose Hosting

Publish an application on Platforms

Continue to entitlement, platform type, deploy/status/logs, and public domain steps.

CDN Hosting/Platforms Default / CNAME / Full DNS
Open platform flow

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Add Your Website
  4. Content Source
  5. Select / buy package
  6. Delivery Method
  7. Related product screen

The combinations users most often need

All 9 combinations can be valid; these examples cover the choices users usually need.

Static file, no domain

Simple Transfer

Upload the file to CDN.com.tr storage and serve it from `xyz.cdn.com.tr`.

Push CDN Default Endpoint
Image or asset subdomain

Serve assets from images.example.com

Files live in CDN.com.tr storage; only the asset subdomain points by CNAME.

Push CDN Custom Subdomain
Existing website

Proxy www.example.com to an existing origin

The origin stays on the customer hosting; CDN.com.tr adds cache, security, and SSL in front.

Pull CDN Custom Subdomain
Full domain management

Move example.com DNS management to CDN.com.tr

Root domain nameservers move to CDN.com.tr; DNS, SSL, and CDN config are managed together.

Pull CDN or Push CDN Full DNS Transfer
Platform preview

Test the app on the default endpoint first

The platform runtime is ready and can be smoke-tested before connecting a public domain.

CDN Hosting/Platforms Default Endpoint
Production app

Connect app.example.com to platform output

Managed Container, PHP, or WordPress output is served from a custom subdomain.

CDN Hosting/Platforms Custom Subdomain

Prerequisites

  • The workload source is known: existing origin, CDN.com.tr storage, or platform runtime.
  • Package purchase is completed in the panel when required.
  • The user knows whether DNS authority or CNAME access is available for the domain model.

Decision model

Where is the content?

Source type describes where the backend lives.

  • Pull CDN: backend is an existing hosting origin.
  • Push CDN: files live in CDN.com.tr storage.
  • CDN Hosting/Platforms: runtime runs on CDN.com.tr.

Which domain serves it?

Delivery method describes the public hostname model.

  • Default Endpoint: `xyz.cdn.com.tr` with no DNS work.
  • Full DNS Transfer: root domain nameservers move to CDN.com.tr.
  • Custom Subdomain: CNAME such as `images.example.com`.

Map combination to a case

The same three delivery methods can be used for Pull, Push, and Hosting/Platforms sources.

  • Push + Default Endpoint: Simple Transfer case.
  • Pull + Custom Subdomain: existing site CDN case.
  • Hosting + Custom Subdomain: platform publish case.

Step-by-step guide

1

Choose the source in the wizard

The Content Source step separates Pull, Push, and Hosting.

  • Choose Pull CDN for an existing origin.
  • Choose Push CDN when files will be uploaded.
  • Choose CDN Hosting when the app runs on CDN.com.tr.

Expected result: The choice determines the later product surface.

cdnctl equivalent 
export CDN_SOURCE=pull
# Alternatives: push or hosting
2

Complete the package prerequisite

If the wizard shows package gating, payment is completed in the panel.

  • Select an eligible purchased package.
  • If no package exists, the user completes purchase in the panel.
  • Record the package ID for automation.

Expected result: Command flows continue with a purchased package ID.

cdnctl equivalent 
# Package purchase is completed in the panel.
cdnctl packages list --owned --format table
export PAID_PACKAGE_ID=<listed_package_id>
3

Choose the delivery method

The delivery step decides how CDN serves the content publicly.

  • Choose Default Endpoint for quick tests without custom DNS.
  • Choose Full DNS Transfer when CDN.com.tr will manage the root domain DNS.
  • Choose Custom Subdomain when only one subdomain will point by CNAME.

Expected result: The account stores source and delivery method together.

cdnctl equivalent 
export DELIVERY_METHOD=default-endpoint
# Alternatives: full-dns-transfer or custom-subdomain
4

Move to the right product screen

After selection, configuration screens diverge.

  • Pull CDN goes to origin and Host header settings.
  • Push CDN goes to File Manager or Push CDN API.
  • Hosting/Platforms goes to platform type, app, and logs.

Expected result: The user does not see unnecessary DNS, upload, or platform steps in the wrong guide.

cdnctl equivalent 
cdnctl cdn accounts create --source "$CDN_SOURCE" --delivery "$DELIVERY_METHOD" --package "$PAID_PACKAGE_ID" --alias selected-flow
export ACCOUNT_UUID=<account_uuid>

Verification

  • Source type and delivery method are explained as separate concepts.
  • Default Endpoint, Full DNS Transfer, and Custom Subdomain appear as common domain models for all source types.
  • Package purchase stays in the panel.
  • The chosen combination points to the right case page.

Use cases

A user is deciding between an existing origin, uploaded static files, or a platform runtime, while also choosing default endpoint, full DNS transfer, or custom subdomain delivery.

Quick workflow

  1. Open the wizard.
  2. Choose Pull CDN, Push CDN, or CDN Hosting as the content source.
  3. Complete the package prerequisite in the panel.
  4. Choose Default Endpoint, Full DNS Transfer, or Custom Subdomain as the delivery method.
  5. Continue to the case page for the selected combination.

Checks

  • This page is not limited to Simple Transfer.
  • The same delivery methods apply to all three source types.
  • cdnctl steps show where the package ID comes from.
  • Screenshots appear as small inline thumbnails next to their step.