Clever Cloud allows you to deploy .NET web applications. This page will explain you how to set up your application to run it on our service.
You do not need to change a lot in your application, the requirements will help you to configure your apps with some mandatory files to add, and properties to setup.
Refer to Quickstart for more details on application creation via the console.
- Make sure you have clever-tools installed locally or follow our CLI getting started guide.
- In your code folder, do
clever create --type <type> <app-name> --region <zone> --org <org>where :
typeis the type of technology you rely on
app-namethe name you want for your application,
zonedeployment zone (
parfor Paris and
orgthe organization ID the application will be created under.
Refer to clever create for more details on application creation with Clever Tools.
- Go to the Clever Cloud console, and find the app you want to fine tune under it’s organization.
- Find the Environment variables menu and select it.
- In this menu, you will see a form with VARIABLE_NAME and variable value fields.
- Fill them with the desired values then select Add.
- Don’t forget to “Update Changes” at the end of the menu.
- Make sure you have clever-tools installed locally. Refer to our CLI getting started.
- In your code folder, do
clever env set <variable-name> <variable-value>
Refer to environment variables reference for more details on available environment variables on Clever Cloud.
You can of course create custom ones with the interface we just demonstrated, they will be available for your application.
The default version used on Clever Cloud is
6.0. You can change it to
5.0 by setting the
CC_DOTNET_VERSION environment variable to
5.0. No support will be provided for end-of-life versions.
Be sure that:
- You have pushed in master branch.
- You listen on port 8080, by default each .NET application is created with the
- You have committed the different files of your project and the corresponding project file (
Let’s take an example with the simple-feed-reader project.
First, you need to add the
APP_FOLDER=SimpleFeedReader environment variable to define the application folder inside the Git repository.
During deployment, the
SimpleFeedReader.csproj file and the target framework
net5.0 are automatically detected. Then, the .NET project is published:
dotnet publish --framework net5.0 --configuration Release
No additional configuration is required (unless multiple project files or target frameworks are present, see the documentation below).
If multiple project files are present in your repository, you can specify the file to use (without the .*proj extension) with the
CC_DOTNET_PROJ environment variable.
If your project file defines multiple targets, like :
You must specify the one you want to run, with the
CC_DOTNET_TFM environment variable.
CC_DOTNET_TFM is specified, then the executable produced by this target is used to start the application.
Make sure to list all your dependencies in your project file. For example:
Compiled dependencies are cached by default to speed up deployments. You can disable dependencies caching completely by removing the
CC_CACHE_DEPENDENCIES environment variable.
If you want to rebuild your application from scratch, you can select “rebuild and restart” from the console or launch
clever restart --without-cache from CLI
The default profile is
Release but you can use the
CC_DOTNET_PROFILE environment variable to change this configuration.
If you need to run a custom command (or just pass options to the program), you can specify it through the
CC_RUN_COMMAND environment variable.
For instance, you can have
Support for private dependencies will be available soon.
Clever Cloud injects environment variables from your application settings as mentioned in setting up environment variables and is also injecting in your application production environment, those from your linked add-ons.
On Clever Cloud you can define some build configuration: like the app folder to deploy or the path to validate your application deployment is ready To do that follow the documentation here and add the environement variable you need.
To access environment variables from your code, you can use
You need Git on your computer to deploy via this tool. Here is the official website of Git to get more information: git-scm.com
The “Information” page of your app gives you your Git deployment URL, it looks like this:
- Copy it in your clipboard
Locally, under your code folder, type in
git initto set up a new git repository or skip this step if you already have one
Add the deploy URL with
git remote add <name> <your-git-deployment-url>
Add your files via
git add <files path>and commit them via
git commit -m <your commit message>
Now push your application on Clever Cloud with
git push <name> master
Refer to git deployments for more details.
By linking an application to an add-on, the application has the add-on environment variables in its own environment by default.
Many add-ons do exist on Clever Cloud: refer to the full list and check add-ons dedicated pages for full instructions.
During add-on creation, an Applications screen appears, with a list of your applications. You can toggle the button to Link and click next. If you finish the process of add-on creation, the application is automatically linked to it.
In the Clever Cloud console, under the Service Dependencies menu of your application, you can use the Link add-ons dropdown menu to select the name of the add-on you want to link and use the add button to finish the process.
You can also link another application from the same page in the Clever Cloud console, using the Link applications dropdown menu.
Need more configuration? To run a script at the end of your deployment? To add your private SSH key to access private dependencies?
Go check the Common configuration page.
You may want to have an advanced usage of your application, in which case we recommend you to read the Administrate documentation section.
If you can’t find something or have a specific need like using a non supported version of a particular software, please reach out to the support.
The healthcheck allows you to limit downtimes. Indeed, you can provide us with paths to check. If these paths return something other than 200, we will consider the deployment as failed.
All you need is add one (or several) environment variable as such:
The deployment process will check all given paths. All of them must reply with a
200 OK response code.
Using the path listed above, below are the expected logs:
Response from GET /my/awesome/path is 200
Response from GET /my/other/path is 500
Health check failed:
- GET /my/other/path returned 500.
If the deployment fails after this message, please update your configuration and redeploy.
In this example, the 1st path is OK, but the 2nd one failed. This give you a hint on what failed in your application.
To make the most of a healthcheck endpoint, you should have it check your critical dependencies. For example:
SELECT 1 + 1;on your database
- retrieve a specific Cellar file
- ping a specific IP through a VPN