Clever Cloud Blog

We have some news about our dear clever-tools, the Clever Cloud CLI for humans, robots and others.

Back in January, we released version 0.10.1 which contained some new commands and a few bug fixes. Today we're releasing version 1.0.0!

You can find all the details about the user oriented changes in the CHANGELOG. In this article, we'll cover the structural changes related to the project:

Improved error handling = better usage in CI/CD pipelines
ES2015 refactor + ESLint = better contributing experience
Goodbye nodegit, hello isomorphic-git!
Improved Jenkins build = more release methods and beta channel (npm, deb, rpm, arch, homebrew and chocolatey)

Now let me tell you the story of this release...

Changes about data privacy are rippling out worldwide, because of the new law from Europe: the GDPR.

Set to take effect on May 25th of this year, this new law restricts the data that companies can collect, and more specifically, how to store and use these data. So, before using any SaaS tool for marketing, sales or analytics, we have to take a step back, and think about the impact this new tool can have on your GDPR data compliance checkist. Open source and self-hosted tools like Mautic significantly reduce the complexity of your compliance checklist (they also have a great post about it).

Mautic provides free and open source marketing automation software available to everyone; free email marketing software, lead management software and more.

This post is about how you can deploy step by step your own Mautic server on Clever Cloud (within a Europe-only zone) using Git.

A few weeks ago I've open sourced issues-helper. It allows you to easily interact with issues on GitHub and GitLab, from the command line.

gli o --assignee clementd --label improvement "Degauss the frobulator fluxfield"

Let's see why and how it's done.

Storing files and assets on Clever Cloud just got easier. After a year of beta testing, we’re proud to release Cellar: a S3-compatible file storage API.

Cellar is faster, cheaper and more reliable thanks to its distributed architecture.

If you’re using FS buckets or storing files in your database, switching to Cellar will make your life easier: files can be directly uploaded to and downloaded from Cellar, without ever going through your application. This way you can handle large files without a hassle.

So, we have been a bit late when it came to supporting PHP 5.6. But we had a good reason for that! We were reworking the PHP scalers to create a single PHP scaler that could handle any PHP versions we would install on it. So we are finally getting PHP 5.6 and 7.0 out in the open.

But that's not all! Previously, selecting your PHP version was done upon application creation once and for all. Changing the PHP version required you to create a new application and to migrate your code (and data).

Now, you can change the PHP version by setting an environment variable and redeploying your application! Just set the PHP_VERSION variable to one of the following values:

5.4
5.5
5.6
7.0

Then redeploy your application, et voilà!

You can now test different versions of PHP as much as you want without setting up your environment every time! In the console, select the PHP (beta) application type when creating a new app. Once the beta will be over, you will see only one PHP option instead of PHP 5.4 and PHP 5.5.