How?

In the console

With Clever-Tools

New-York, USA -> nyc
Paris, France -> par
Montréal, Canada -> mtl
Singapore, Singapore -> sgp
Roubaix, France -> rbx
Warsaw, Poland -> wsw
Sydney, Australia -> syd

• We are changing the way we measure consumption, prices remain the same.
• Uptime was billed by 10 minutes slices, it's now billed by one second slices.
• You will be able to use credits for everything: Applications, Add-ons, custom tasks you ask to the support team.
• Invoices will display every detail about your consumption.
• Changing measurement should not have any major impact on your invoices.

Second based prices

Consume everything with Credits

An invoice with every details

There have been some changes in licensing models for certain software vendors recently, Elastic in particular. While we are not going to go over those in detail, we want to reassure you that Clever Cloud is an Elastic official partner, and as such nothing changes for our customers. We will continue to support and extend our Elastic integration.

Now that it has been cleared out let me tell you more about how we envision partnership at Clever Cloud. We believe that Cloud providers, as infrastructure providers, should be enablers of other Software Vendors. It might seem like a triviality but seeing how some other cloud providers behave, it seems unclear.

Responsabilities as a Service

A cloud provider is infrastructure. Infrastructure is a necessary condition to business. Being necessary can put you in an abusive position. It’s even more true when you have a monopolistic position on a market. Basically you can behave like a bully or a child.

If you want to address AWS or the Apple store users, you have to play by their rules. And the bigger they are the more they get to decide what rules apply. This also gives them power to retaliate.

They could for instance tell the world they are in a partnership with you while it’s false. Some will take it for granted because they don’t necessarily know you. Then offer the same service without giving back, capitalizing on all the efforts made by the vendor and its community.

Here we need to state that laws and regulations have always lagged behind innovation in the Software industry. This is partly the reason why we see new Software licences(AGPL, SSPL and the likes) being adopted to protect IPs or trademarks from possible abuse.

That’s not right. Usually supporters of these methods will answer something like “yes but it’s legal”. Resorting to this authority argument usually means you have nothing else to say and know you are losing ground on everything else. (and in Elastic’s case, the “it’s legal” argument hardly holds as AWS has been abusing Elastic’s trademark).

It’s about doing the right thing. Don’t be a bully.

Because we think it’s important to do what’s right, we have always had the following approach towards Vendors.

Before providing anything as a service we propose a revenue sharing model: the vendor gets a cut of the money we made with the product. This is currently the best way we found to respect a cloud consumption/pay as you go model. Granted this goes against the traditional yearly subscription model and how sales teams traditionally operate. But we are talking about a partnership here.

What can Clever Cloud bring you?

If this is of interest to you let's go quickly over some Clever Cloud facts.

• Clever Cloud is a European company and as such is not subjected to the US Cloud Act.
• It works as a public, private, hybrid or on-premises cloud, and is available on other public Cloud like OVH, and several others are planned this year.
• As our infrastructure and orchestrator is proprietary we will manage all the product integration, which usually results in 0 integration cost for the vendor.
• We will handle level1/level2 support.

When integrating a product we make sure we don't require any help from the vendor, to result in us sending them money every quarter without any effort on their part. They should not have to engage resources. It’s our job to provide this for them. This situation is often reversed because of the monopolistic situation of the major Cloud providers.

Let it be known that we always come to vendors with this proposal when considering to add their product to our catalog. And we have had a wide range of reactions. From “why would you give me money this is open source” to “You need to buy this much upfront. If you can’t why don’t you ask your VCs to pitch in ?”. And everything you can think of in the middle.

Again, Cloud providers must be enablers for software vendors.

Our Technical Differencies

Running a cloud platform is something technical and as such we have several specificity you may want to know about:

There is always a point in our conversation where we talk about how the vendor support team can only support us if we use this specific version of Linux. And as it turns out we use a different version than most. We rely on Exherbo, an upstream, source based distribution. Here's two main points to why.

Being upstream allows us to use the latest version of each software, with the latest security patches. Look there was a time where it was super important to be on a battle-tested version of X or y. Because the primary security issue was to avoid segfault. It was a software stability issue. it's 2021. Things have changed. The main security concern is to have your SSL library up to date to protect yourself from external attack. Take the heartbleed security bug for instance. Our infrastructure was long patched when this became a known issue.

Being source based allows us to be in control. We can patch all our infrastructure faster. And since we compile everything we make sure it's optimized for the hardware it runs on. Most other distributions are just compiled to support everything, so it's optimized for nothing. It's the price to pay for genericity.

This is also the reason why as a PaaS provider we encourage people to simply deploy their source code instead of an unoptimized binary. And why when we provide closed source solutions, we are more than happy to sign an NDA to access the sources and make sure it's compiled for our platform. In this process we are also more than happy to contribute anything we may find interesting.

Become a Registered ISV

Now you should have a fairly good understanding of our partnership vision, and the role we envision for Cloud providers in our global economy. If you are a software vendor looking for a partnership, we would be happy to talk :)

Simply send us an email to devrel@clever-cloud.com.

Today we are releasing an updated, rebranded version of our documentation.

It has been a change long in the making, we have a new documentation portal. New layout, new organization, new content but it's still available at the same place: https://www.clever.cloud/developers/

The content still lives under https://github.com/CleverCloud/doc.clever-cloud.com/ and has been reorganized. We are, of course, always welcoming new contributions, whether it is for a single typo, filling an issue or a detailed tutorial. Guidelines are available on the 'Writing new Content' page.

Please give us feedback. We would love to know what page is missing or what you would like to read.

A quick word about how it's made. We are using Hugo to generate the website. The theme used for this website is also available on Github: https://github.com/CleverCloud/hugo-cc-doc-theme

One of the reasons for this choice is that we are selling white-label version of Clever Cloud, and our customers want their own documentation. This allows us to keep working on the same content and to offer them a quick and easy way to deploy their own documentation.

I would like to finish this post with a big thank you to Valeriane Venance who started this project with me and made a good chunk of it, to the Clever Cloud team and to all our contributors.

How!?

In the console

With Clever-Tools

• Paris, France -> par
• Montréal, Canada -> mtl
• Singapore, Singapore -> sgp
• Roubaix, France -> rbx
• Warsaw, Poland -> wsw
• Sydney, Australia -> syd

Create a Cellar Addon

Using the CLI

Using the Web Console

Setup a Bucket

<?xml version="1.0" encoding="UTF-8"?>
<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Name>ldoguinbucket</Name>
<Prefix></Prefix>
<MaxKeys>1000</MaxKeys>
<IsTruncated>false</IsTruncated>
<Contents>
    <Key>hello.txt</Key>
    <LastModified>2020-10-05T13:07:08.664Z</LastModified>
    <ETag>&quot;b1946ac92492d2347c6235b4d2611184&quot;</ETag>
    <Size>6</Size>
    <StorageClass>STANDARD</StorageClass>
    <Owner>
        <ID>cellar_0e275449-c02a-4e07-b100-2e357b532e3b</ID>
        <DisplayName>cellar_0e275449-c02a-4e07-b100-2e357b532e3b@user_51f7098f-604e-4d9e-8fb6-4026fd1767bb</DisplayName>
    </Owner>
    <Type>Normal</Type>
</Contents>
<Marker></Marker>
</ListBucketResult>

Add the Listing

git clone https://github.com/qoomon/aws-s3-bucket-browser/ 
s3cmd put --acl-public aws-s3-bucket-browser/favicon.ico s3://your-unique-bucket-name/favicon.ico
s3cmd put --acl-public aws-s3-bucket-browser/index.html s3://your-unique-bucket-name/index.html
s3cmd put --acl-public aws-s3-bucket-browser/logo.png s3://your-unique-bucket-name/logo.png

Domain Redirection

Create the Bucket

Upload your Site

export RCLONE_CONFIG_MYS3_ACCESS_KEY_ID=$CELLAR_ADDON_KEY_ID
export RCLONE_CONFIG_MYS3_SECRET_ACCESS_KEY=$CELLAR_ADDON_KEY_SECRET
export RCLONE_CONFIG_MYS3_ENDPOINT=$CELLAR_ADDON_HOST
export RCLONE_CONFIG_MYS3_TYPE="s3"

Build and Upload your Static Site

mkdir hugo-cellar-static # Create the site root folder
cd hugo-cellar-static/
hugo new site . # Generate a new Hugo site
git init # initialize the git repository
git submodule add https://github.com/jakewies/hugo-theme-codex themes/codex # add a theme
cp themes/codex/exampleSite/config.toml config.toml # copy the default configuration
cp -r themes/codex/exampleSite/content/ . # copy default content for the exemple
gedit config.toml  # edit the configuration, like the theme or the baseUrl
clever create --type static-apache myapp # Create a new clever cloud application
clever service link-addon MyCellar # link the app to the Cellar add-on 
cat ~/.config/clever-cloud  # Get the clever-tools token

CC_PHP_VERSION="7"
CC_PRE_RUN_HOOK="./hugo.sh" # A prerun hook to execute the build and sync it to Cellar
CC_RUN_SUCCEEDED_HOOK="clever stop" # use clever-tools to turn off the app when finished 
CLEVER_SECRET="xxxx" # Tokens for clever-tools
CLEVER_TOKEN="xxxxx" # Tokens for clever-tools
DL_RCLONE_VERSION="1.52.1" # which version of rclone to use
HUGO_VERSION="0.62.0" # which version of hugo to use
MY_DOMAIN="blog.ldoguin.name/" # The name of the bucket to sync
PORT="8080"
HUGO_ENV="production"

# Configure rclone Cellar connection
export RCLONE_CONFIG_MYS3_ACCESS_KEY_ID=$CELLAR_ADDON_KEY_ID
export RCLONE_CONFIG_MYS3_SECRET_ACCESS_KEY=$CELLAR_ADDON_KEY_SECRET
export RCLONE_CONFIG_MYS3_ENDPOINT=$CELLAR_ADDON_HOST
export RCLONE_CONFIG_MYS3_TYPE="s3"

# Download and unpack rclone and hugo
wget https://downloads.rclone.org/v$DL_RCLONE_VERSION/rclone-v$DL_RCLONE_VERSION-linux-amd64.zip
wget https://github.com/gohugoio/hugo/releases/download/v$HUGO_VERSION/hugo_extended_"$HUGO_VERSION"_Linux-64bit.tar.gz
unzip rclone-v$DL_RCLONE_VERSION-linux-amd64.zip
tar xvf hugo_extended_"$HUGO_VERSION"_Linux-64bit.tar.gz

# Execute the site generation with Hugo
chmod +x ./hugo
./hugo --gc --minify

# Sync the site to Cellar
./rclone-v$DL_RCLONE_VERSION-linux-amd64/rclone sync ./public mys3:$MY_DOMAIN --progress --s3-acl=public-read

git add .  # add the current folder to git
git commit -m"init" # commit
clever deploy # Deploy your website

Create a new Hugo website

mkdir mysite
cd mysite
hugo new site .
git init
git submodule add https://github.com/mattstratton/castanet themes/castanet
cp themes/castanet/exampleSite/config.toml config.toml 
git add .
git commit -m'init'

Deploy to Clever Cloud

wget https://github.com/gohugoio/hugo/releases/download/v$HUGO_VERSION/hugo_extended_"$HUGO_VERSION"_Linux-64bit.tar.gz
tar xvf hugo_extended_"$HUGO_VERSION"_Linux-64bit.tar.gz
chmod +x ./hugo
./hugo --gc --minify --destination public/fr/podcast

clever create --type static-apache mysite
clever domain add clever-cloud.com/fr/podcast
clever config set force-https enabled
clever env set CC_PRE_BUILD_HOOK "./hugo.sh"
clever env set CC_WEBROOT "/public"
clever env set HUGO_ENV "production"
clever env set HUGO_VERSION "0.68.3"
clever deploy

Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.

git init
npm init

wget https://github.com/denoland/deno/releases/download/$DENO_VERSION/deno-x86_64-unknown-linux-gnu.zip
unzip deno-x86_64-unknown-linux-gnu.zip

chmod +x installdeno.sh

clever create --type node myDenoApplication

clever env set CC_PRE_BUILD_HOOK ./installdeno.sh
clever env set DENO_VERSION v1.0.0 

import { Application } from "https://deno.land/x/abc/mod.ts";

const app = new Application();

app
  .get("/", (c) => {
    return "Hello, Abc!";
  })
  .start({ port: 8080 });

{
  "name": "abc-test",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "start":"./deno run --allow-net abc.js",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

git add abc.js installdeno.sh package.json
clever deploy

• environment variables injection
• monitoring & alerting (auto restart)
• zero downtime deployments
• metrics (data & charts)
• live logs
• automatic scalability

$ clever tcp-redirs add --namespace cleverapps
Successfully added tcp redirection on port: 21562

$ clever tcp-redirs list-namespaces
Available namespaces: default, cleverapps

$ git clone https://github.com/CleverCloud/tcp-chat
$ cd tcp-chat
$ clever create --type node tcp-chat
$ clever tcp-redirs add --namespace cleverapps
$ Successfully added tcp redirection on port: 21562
$ clever domain add mychat.cleverapps.io
$ telnet mychat.cleverapps.io 21562