Home | Blog | Weekly Platform Update #24

Weekly Platform Update #24

wpu24 1

By Clément Nivolle

Features

The Weekly Platform Update is a series of posts about every impactful changes on Clever Cloud. You’ll find the updated parts of Clever Cloud below, to follow fixes, updates, new products and more on a weekly basis.

Core

  • All runtimes: updated to linux 4.12.4
  • rust: rustup updated (stable 1.19.0)
  • python : fixed malformed json logging function not defined, updated command-logger
  • node: updated to 8.1.2

Doc

  • Various updates on Rails
  • new section for secret generation in Play2!
  • updated php-apps hooks
  • laravel support added
  • the FAQ got a tiny refresh

Products

  • Console : Fixed an issue where users with the DEV role couldn’t create applications
  • Metrics (beta): improvements for java and global UI improvements
  • Deployment emails: link to the to logs page opens the current deploying instance
  • Wording improvements in billing related emails
  • New PDF invoice design

Tags

Blog

À lire également

HDS migration: migrate your healthcare data with no perceptible downtime
An HDS migration consists of transferring an application and its healthcare data from one hosting provider to another while maintaining the required certification and service continuity. When properly planned and executed, the perceived interruption can be reduced to a simple DNS switch. For example, when Madietenligne, a provider of an e-health solution for dietitians, migrated to Clever Cloud, its test and production environments were moved in less than fifteen days, covering 500 GB of data, with no downtime perceived by users.
Features

Gravitee and Clever Cloud Announce Strategic Partnership for European AI Sovereignty 
Gravitee and Clever Cloud Provide an Open-Source, Deploy-Anywhere Control Plane Ensuring European AI Runs Strictly on Your Terms.
Press

Magnetar: a Rust Apache Pulsar client built for deterministic simulation
Some of the most interesting reliability work in distributed systems starts with a simple idea: if a system can fail in production because of time, scheduling, networking, or unlucky interleavings, then those forces should be brought into tests under control.
Engineering