Home | Blog | Weekly Platform Update #33

Weekly Platform Update #33

wpu33 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.

[Unreleased]

  • console: a new log viewer
  • console: clever cloud metrics & improvments

WPU #33 – 2018-01-12

Added

  • documentation: A PHP Symfony article has been added: https://www.clever.cloud/developers/php/tutorial-symfony
  • java: The JVM agent gathering GC-related metrics for java applications can be disabled (as it can interfere with spring boot applications) with CC_DISABLE_JVM_AGENT set to true in the application’s environement variable.
  • java: new support of Play v1.5

Changed

  • all runtimes: various linux updates to adress Meltdown and Spectre (linux 4.14.11)
  • rust: rustup update
    • stable 1.23.0
    • beta 1.24.0-beta.1
    • nightly 1.24.0-nightly

Removed

  • php: hiding varnish compiled data in logs

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