Domain names

When creating an application, you have two (non-exclusive) choices for domain names:

• Using a personal domain name
• Using a cleverapps.io free domain for dev purposes, with built-in SSL

Add it in the application configuration: in the console, click application name in the first panel, then choose domain names. You’ll have to choose to add a custom domain name or use a subdomain under *.cleverapps.io.

Using a *.cleverapps.io free domain, with built-in SSL

In the console, in the domain name sub menu of your application, there is a default entry configured by default for every new app: yourAppID.cleverapps.io, which can be removed.

In your application’s domain section, just enter example.cleverapps.io. You have to choose a unique one. Trusted SSL is available on every subdomain.

Using Personal Domain Names

You can point your domain name to Clever Cloud either with a CNAME record or with A records.

The use of a CNAME record is highly recommended.

With a CNAME record, your DNS configuration is always up-to-date. Using A records will require you to keep the DNS configuration up-to-date manually.

We also support wildcard personal domain names, to do so use the standard pattern to describe it: *.example.com

Your Application Runs in the Europe/Paris (‘PAR’) Zone

Provide the following to your registrar:

Your Application Runs in the Europe/Paris onto Scaleway (‘SCW’) Zone

Your Application Runs in the Europe/Roubaix (‘RBX’) Zone

Your Application Runs in the Europe/Roubaix HDS (‘RBXHDS’) Zone

Your Application Runs in the Europe/Warsaw (‘WSW’) Zone

Your Application Runs in the Europe/Gravelines (‘GRAHDS’) Zone

Your Application Runs in the North-America/Montreal (‘MTL’) Zone

Provide the following to your registrar:

Your Application Runs in the Asia/Singapore (‘SGP’) Zone

Your Application Runs in the Oceania/Sydney (‘SYD’) Zone

If you want to make your application available from a domain name which does not support CNAME records (eg example.com in addition to www.example.com), check if your registrar provides a web redirection service. This way, you only have to make www.example.com point to Clever Cloud. Please note that web redirection provided by registrars only work over HTTP.

Remember that DNS changes may take time to propagate (usually a few hours, sometimes up to a day or more). It depends on the TTL setting of your DNS configuration. For faster changes, you can lower the TTL value in advance, and rise it again afterwards.

Contextual Example

Path routing

Requests are routed to applications based on the domain name, but you can also route depending on its path.

For instance, you can bind example.com to an app, and example.com/api to another one. All the HTTP requests on example.com where the path starts with /api will be routed to the second app. The other requests will be routed to the first app. You can add a path after every domain name you bind in the console (or with clever tools).

Note that your path-routed application needs to have a /whatever route.

This will work:

example.com        ->      myfirtapp-main-route

example.com/api    ->      mysecond-app-main-route/api

This will NOT work:

example.com        ->      myfirtapp-main-route     (works)

example.com/api    ->      mysecondapp-main-route   (404 response from mysecondapp)

Path routing for static sites

In the case of static files, you usually understand routes as paths in a file tree.

This will work:

example.com/api    ->     my-static-site/api/index.php

This will NOT work:

example.com/api    ->     my-static-site/index.php

Gandi CNAME configuration

Here is an article that demonstrates a simple setup for Gandi CNAMEs.