FS Buckets configured with Environment Variables

fsb envvar 1

For a long time the only way to configure an FS Bucket for your application was to create a buckets.json file in ./clevercloud/ and specify the configuration in there. Not very Immutable Infrastucture friendly. It ends today.

Because you had to write a file in your code for a specific application, it made your code repository tied to a particular application. Sure there was a workaround with the apps field that allowed us to whitelist applications for each buckets. But it is still more painful than it should be.

Well starting today you can configure FS Buckets using environment variable. Here's what you need to add:

CC_FS_BUCKET=/path/to/folder:bucket_host

So if you have the following file:

[
  {
    "bucket_host": "bucket-c65762b6-4086-4c99-84b0-23eb85695809-fsbucket.services.clever-cloud.com",
    "folder": "/sites/default/files"
  }
]

You can delete it and replace it with the environment variable CC_FS_BUCKET=/sites/default/files:bucket-c65762b6-4086-4c99-84b0-23eb85695809-fsbucket.services.clever-cloud.com.

If you have multiple buckets you can use multiple variables like so:

CC_FS_BUCKET=/path/to/folder:bucket_host
CC_FS_BUCKET_0=/path/to/folder:bucket_host
CC_FS_BUCKET_10=/path/to/folder:bucket_host

Blog

À lire également

UP Program: Clever Cloud announces its fifth startup selection

With this new batch, Clever Cloud welcomes four startups to the UP Program: Sentibee, Pictaderm, Legaia and Cockpit Agriculture.
Company

Sōzu 2.0 — turning a reverse proxy into a programmable edge

Sōzu is the reverse proxy that sits in front of every application running on Clever Cloud. After eighteen months of work — first the HTTP/2 multiplexer, built on our existing kawa pivot, then almost every other layer of the proxy, and finally a long run in production on the cleverapps.io load balancers — Sōzu 2.0 is out.
Engineering

K3s vs K8s: What Are the Differences and Which One Should You Choose in 2026?

Kubernetes has become the standard for container orchestration. But depending on your infrastructure constraints (limited resources, edge computing, IoT, or large-scale enterprise clusters), the distribution you choose can radically change the operational experience. K3s and K8s (upstream Kubernetes) address different needs, even though both share the same CNCF-certified foundation.
Engineering Features