Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how Built your app with AI? From folder to live URL with one command — no git, no registry: cdnctl deploy. See how Code on GitHub? Every push auto-deploys to cdn.com.tr — connect your repo and ship. See how

CDN.com.tr Help

Host static content with Simple Transfer

In the Add Your Website wizard, choose Push CDN as the content source and Default Endpoint as the delivery method, then publish files from the generated CDN.com.tr endpoint.

Getting started

Host static content with Simple Transfer

In the Add Your Website wizard, choose Push CDN as the content source and Default Endpoint as the delivery method, then publish files from the generated CDN.com.tr endpoint.

Where to go after this flow

After default-endpoint publishing starts, users often need a custom domain, purge, or deploy verification.

Custom domain

Move from default endpoint to CNAME or Full DNS

If the same Push CDN source will later serve from images.example.com or the root domain, review the choice model.

Push CDN CNAME / Full DNS
Open choice guide
Deploy verification

Apply Changes and watch Operations

Check whether delivery or storage changes reached traffic config.

Push CDN All delivery methods
Open apply guide
Concept + CLI

How CDN file storage works (panel and cdnctl)

Learn what serving files from the CDN means, and upload from the panel or with the scp-like cdnctl cp command.

Push CDN File storage
Read the guide

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Add Your Website
  4. Content Source: Push CDN
  5. Select / buy package
  6. Delivery Method: Default Endpoint
  7. Generated xyz.cdn.com.tr endpoint
  8. Push CDN File Manager or API
  9. Public URL verification

Prerequisites

  • The user is signed in and can open CDN Accounts.
  • The required package must be purchased in the panel and assigned to the account; payment is not an API or AI-agent task.
  • This scenario does not require a custom domain, CNAME, nameserver change, or SSL certificate.
  • If the browser blocks the File Manager window, allow popups for cdn.com.tr.

Decision model

1. Content source

The wizard first asks where the content comes from.

  • Pull CDN: an existing hosting origin is placed behind CDN.com.tr.
  • Push CDN: files are uploaded to CDN.com.tr storage. Simple Transfer starts here.
  • CDN Hosting/Platforms: the app or platform runs on CDN.com.tr.

2. Delivery method

After the source is chosen, select which domain model serves that content.

  • Default Endpoint: serves from xyz.cdn.com.tr without DNS work.
  • Full DNS Transfer: the domain nameservers move to CDN.com.tr and DNS management unlocks the full feature set.
  • Custom Subdomain: a subdomain such as images.example.com CNAMEs to xyz.cdn.com.tr.

This case combination

Simple Transfer static hosting uses the Push CDN + Default Endpoint combination.

  • Pull CDN + Default Endpoint gives an existing origin a default endpoint.
  • Push CDN + Full DNS Transfer serves uploaded files from the customer root domain.
  • Hosting/Platforms + Custom Subdomain serves platform output from a subdomain.

Step-by-step guide

1

Start the wizard from CDN Accounts

After signing in, open /en/management/cdn and click Add Your Website at the top.

  • The button uses the CdnAccount.vue wizardUrl to open the setup wizard.
  • The new account flow starts with content source selection.

Expected result: The Content Source screen shows Pull CDN, Push CDN, and CDN Hosting options.

cdnctl equivalent 
cdnctl update --check
cdnctl login
cdnctl accounts list
2

Choose Push CDN as the content source

For simple static hosting, the origin is not the customer server; the source is CDN.com.tr storage.

  • Select the Push CDN card.
  • Continue to the package step.

Expected result: The wizard carries the selected content source value as push.

cdnctl equivalent 
export CDN_SOURCE=push
3

Complete the package step

The wizard lets the user select an eligible package or routes them through manual purchase in the panel when needed.

  • Select an eligible package when one exists.
  • If no package is available, the user completes purchase in the panel.
  • Continue in the wizard after the package is ready.

Expected result: API, cdnctl, or AI-agent workflows do not start before payment is complete.

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

Choose Default Endpoint as the delivery method

When the delivery method step asks how CDN should serve the content, Default Endpoint avoids DNS and custom-domain work.

  • Select the Default Endpoint card.
  • Confirm that Full DNS Transfer and Custom Subdomain are not required for this case.
  • Finish the wizard.

Expected result: The system creates the account with is_basic_transfer and returns a default service name like xyz.cdn.com.tr.

cdnctl equivalent 
export ACCOUNT_UUID=<account_uuid>
export ENDPOINT=<endpoint>.cdn.com.tr
5

Upload the file to CDN.com.tr storage

After the account exists, use Push CDN File Manager or Push CDN API to upload the file to the selected account.

  • Open File Manager from Push CDN or get an API token.
  • Choose root / or a target folder.
  • Upload a static file such as hello.txt, logo.png, or app.css.

Expected result: The uploaded file appears in the selected account storage area.

cdnctl equivalent 
cdnctl files put --account "$ACCOUNT_UUID" --file ./hello.txt --target-path /hello.txt
cdnctl files ls --account "$ACCOUNT_UUID"
6

Verify the public URL

Combine the generated default endpoint with the file path.

  • Open a URL in the form https://xyz.cdn.com.tr/hello.txt.
  • Use a private or clean browser session.
  • If old content appears, purge the path from Purge Management and try again.

Expected result: The public URL returns 200 and serves the uploaded static content from the default CDN.com.tr domain.

cdnctl equivalent 
curl -I "https://$ENDPOINT/hello.txt"

Verification

  • The wizard content source is Push CDN.
  • The delivery method is Default Endpoint.
  • The generated xyz.cdn.com.tr endpoint can be used without a custom domain.
  • The file name in File Manager matches the public URL path.
  • Successful test screenshots should show the CDN Accounts button, Push CDN source selection, package step, Default Endpoint selection, generated endpoint, upload result, and public URL verification.

Use cases

A customer wants to serve static assets quickly without connecting their own domain; files live in CDN.com.tr storage.

Quick workflow

  1. Open CDN Accounts and click Add Your Website.
  2. Choose Push CDN in the Content Source step; the files will live in CDN.com.tr storage.
  3. Select an existing package or complete manual package purchase in the panel.
  4. In the step that asks how CDN should deliver the content, choose Default Endpoint.
  5. Copy the generated xyz.cdn.com.tr endpoint.
  6. Upload the file through Push CDN File Manager or API.
  7. Verify https://xyz.cdn.com.tr/<path> publicly.

Checks

  • In this guide, Simple Transfer means Push CDN + Default Endpoint.
  • Uploaded object belongs to the selected account.
  • Default delivery domain is shown without requiring DNS.
  • No custom CNAME or certificate step is required for the first publish.
  • Full DNS Transfer and Custom Subdomain are separate delivery options available across source types.