Account and access

Site addresses and domains

How your site's address is set, what happens to it when you rename the project or add and delete environments; connecting your own domain to your site.

Open as plain text

Every environment has an address; it is shown in the environment's header once the environment is live. This page explains how the address is set, what happens when it changes, and how to connect a domain you own to your site.

#How the address is set

The address comes from the project's name and is opened under your installation's site domain. In the example, the project is named blog:

If the project has a single environment, the address is the project's name: blog.<site domain>.
If there are two or more environments, the topmost environment gets the project's name (prod first, then stage, then dev); the others get the environment's name added to their address: prod blog, dev blog-dev.
Turkish letters are simplified (güzel → guzel), and characters other than letters and digits become hyphens.
If the name is already taken by another project, a number is added to the end of the address (blog-2). Some names are reserved for the platform itself; if you choose one of them, the address is derived differently. In both cases the panel shows the new address in advance.

You can always see the environment's full address in its header.

#When adding and deleting environments

When you add a higher environment to the project (for example prod when there is only dev), the project's name moves to the new environment; the previous environment moves to an address with its environment name. The environment creation dialog shows in advance how the addresses will change. The new environment is empty until its first release.
When you delete an environment and only one environment will remain in the project, the delete dialog asks whether the remaining environment's address should become the project's name. The box comes unticked; if you leave it unticked, the remaining environment's address does not change.
The deleted environment's address stays reserved for your tenant only for 30 days; during that time no other tenant can take it.

#Renaming the project

Open the dialog
In the project's settings, in the Proje adı ve adresler (Project name and addresses) section, press the «Projeyi yeniden adlandır» (Rename project) button.
Type the new name
As you type in the «Yeni ad» (New name) field, the dialog shows each environment's current and new address.
Choose what happens to the old address
If the addresses change, choose one for the old address: «Hemen kapat» (Close now) or redirecting the old address to the new one for a set period (at most 15 days).
Save
Press the «Yeniden adlandır» (Rename) button.

When the address changes, your app is not restarted; the site opens at the new address right away.
Old addresses whose redirect is still running are listed in the Proje adı ve adresler (Project name and addresses) section; «Şimdi kapat» (Close now) closes one without waiting for the period to end. A closed address stays reserved for your tenant only for 15 days.
If the address scheme is off, or the new name gives the same address, only the project's display name changes.
A member with the «Kiracı yöneticisi» (Tenant admin) or «Geliştirici» (Developer) role can rename the project.

#Your app when the address changes

Turguz gives your app the site's address in the TURGUZ_ADRES variable. When the address changes, the running app keeps knowing the old address; it learns the new one at the next deployment or when it restarts. A strip saying so appears on the environment's Genel bakış (Overview) tab. If your app doesn't use its own address to build links, you don't need to do anything.

If the old address appears in your variables (for example a sign-in provider's return address), the Değişkenler (Variables) tab offers to update them with the new address.
You update the addresses registered with outside services, such as sign-in providers (Google, GitHub and so on) and payment systems, in that service's own panel.

#Connecting your own domain

You can connect your own domain (such as www.example.com) to an environment or to a server's published service. The site keeps opening at the address Turguz gave it, too.

Add the domain
For an environment, open the Alan adı ve erişim (Domain and access) section on the environment's Ayarlar (Settings) tab; for a server's published service, open the Yayınlar (Published services) section in the server's details. On the Kendi alan adınız (Your own domain) card, type the domain into the «Bağlanacak alan adı» (Domain to connect) field and press the «Alan adı bağla» (Connect domain) button.
Write the DNS record
The card shows the record you need to create in your domain's DNS panel: the record type, name and value. Copy the values from the card and enter them in the DNS panel of the place where you got your domain.
Verify
Once the record has spread, press the «Doğrula» (Verify) button. Turguz also tries the record on its own at regular intervals. For a verified domain, a secure connection (HTTPS) is prepared automatically; this can take a few minutes. You get a notification when it is ready.

For a subdomain such as www.example.com, a CNAME record is used.
A root domain (example.com, without www) can't take a CNAME record. The card first suggests www.example.com: you open the site at the www name and point example.com to the www address with the forwarding feature of the place you bought the domain from. This works with every provider. If you accept the suggestion, the root domain request is removed; you can still connect the root domain later. Some providers' forwarding only works with http://; in that case connect the root domain in one of the ways below.
There are two ways to connect the root domain directly; one is enough. If your provider supports a CNAME-like record at the root (it's called ALIAS, ANAME or CNAME flattening), use it: your connection keeps working even if the platform's address changes. If not, add an A record.
If you also add an ownership record (TXT) for the root domain, the connection opens without waiting for admin approval. Its value is unique to you; copy it from the card. Without it, once the record is verified the connection goes to the platform admin for approval and the decision comes as a notification. While waiting for approval, you can add the TXT record and press «Doğrula» (Verify) to skip the wait.
Don't add an AAAA record; if you do, some visitors can't reach your site.
Some DNS panels want only the first part of the name, not the whole domain: @ (or empty) for the root domain, www for www.example.com, _turguz-dogrulama for the ownership record.
If your DNS provider puts the record behind its own proxy, turn that off until verification is done; while it is on, Turguz can't see your record.
A domain that isn't verified drops off by itself after 7 days; you need to add it again.
There is an upper limit on the number of domains a tenant can connect; when you reach it, the panel says so.
You disconnect a connected domain with «Kaldır» (Remove) on the card. To connect it again, DNS verification starts over.
To add, verify and remove domains, you need the «Kiracı yöneticisi» (Tenant admin) or «Geliştirici» (Developer) role.

To open your site only to specific addresses: Allowed addresses. To make an app running on a server available on the internet: Publishing the application on a server.