CDN.com.tr Help

Simple Transfer static hosting

Use the Add Your Website wizard to choose Push CDN + Default Endpoint and publish static files from the generated default CDN.com.tr domain.

Back to Help Center Back to section

Case studies

Simple Transfer static hosting

Use the Add Your Website wizard to choose Push CDN + Default Endpoint and publish static files from the generated default CDN.com.tr domain.

Panel path

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

Prerequisites

  • The user is signed in and can open CDN Accounts.
  • The required package is purchased in the panel and assigned.
  • This case does not require a custom domain, CNAME, nameserver change, or SSL certificate.

Decision model

Source type

This case must use Push CDN because files are placed in CDN.com.tr storage.

  • Pull CDN is for an existing origin.
  • Push CDN is for uploaded static files.
  • CDN Hosting/Platforms is for workloads running on CDN.com.tr.

Delivery method

This case must use Default Endpoint because it does not use the customer domain.

  • Default Endpoint: `xyz.cdn.com.tr`.
  • Full DNS Transfer: the domain nameservers move to CDN.com.tr.
  • Custom Subdomain: `images.example.com` CNAMEs to the default endpoint.

Step-by-step guide

1

Start from CDN Accounts

The case study starts from the Add Your Website button in the CDN account list.

  • Open CDN Accounts.
  • Click Add Your Website.
  • Confirm the wizard opens the Content Source step.

Expected result: The wizard shows Pull CDN, Push CDN, and CDN Hosting options.

cdnctl equivalent 
cdnctl update --check
cdnctl login --email "<email>" --password "<password>"
cdnctl accounts list
2

Choose Push CDN and package

Simple Transfer requires the file to live on CDN.com.tr.

  • Choose Push CDN in the Content Source screen.
  • Select an existing package or complete manual purchase in the panel.
  • Continue in the wizard after purchase is complete.

Expected result: The source type continues as `push`, and the package prerequisite is solved in the panel.

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

Create the account with Default Endpoint

Selecting Default Endpoint in the delivery method step avoids custom DNS work.

  • Choose Default Endpoint.
  • Finish the wizard.
  • Copy the generated `xyz.cdn.com.tr` endpoint.

Expected result: The account is ready to serve from the default CDN.com.tr endpoint.

cdnctl equivalent 
cdnctl cdn accounts create --source push --delivery default-endpoint --package "$PAID_PACKAGE_ID" --alias simple-transfer-demo
export ACCOUNT_UUID=<account_uuid>
export ENDPOINT=<endpoint>.cdn.com.tr
4

Upload and publish the file

File Manager or Push CDN API stores the file on the selected account.

  • Open Push CDN File Manager or get an API token.
  • Choose root `/` or a target folder.
  • Upload the static file.
  • Open `https://xyz.cdn.com.tr/<path>` in a clean browser session.

Expected result: The static file returns 200 from the default CDN.com.tr domain without a custom domain.

cdnctl equivalent 
cdnctl push files upload --account "$ACCOUNT_UUID" --file ./hello.txt --path /hello.txt
cdnctl push files list --account "$ACCOUNT_UUID"
cdnctl cdn accounts apply --account "$ACCOUNT_UUID"
curl -I "https://$ENDPOINT/hello.txt"

Verification

  • The Content Source step shows Push CDN selected.
  • The delivery method step shows Default Endpoint selected.
  • The generated default endpoint is visible.
  • File Manager shows the uploaded file.
  • The public URL returns 200.

Use cases

A customer needs static asset hosting without connecting their own domain; files live in CDN.com.tr storage and are read from `xyz.cdn.com.tr`.

Quick workflow

  1. Open CDN Accounts and click Add Your Website.
  2. Choose Push CDN in the Content Source step.
  3. Complete the package prerequisite.
  4. Choose Default Endpoint when the wizard asks how CDN should deliver the content.
  5. Copy the generated default CDN.com.tr endpoint.
  6. Upload the file through File Manager or API.
  7. Verify the public URL from a clean browser session.

Checks

  • No CNAME is required.
  • The default delivery domain is shown clearly.
  • Screenshots prove wizard selection, upload, and public read success.
  • The same three delivery methods should be considered for Pull CDN, Push CDN, and Hosting/Platforms sources.

Related pages

First paid CDN account

For the first paid CDN account case, use the Getting Started page that defines the account, package, and cdnctl boundary.

Existing website through CDN

For the existing website case, use the Getting Started Pull CDN chain covering Host header, DNS, SSL, and Apply Changes.

Platform application publish

For the platform application case, use the Getting Started entitlement, Hosting/Platforms, deploy/status/logs, and delivery chain.