Cockpit stores data in local file system - even though mongodb used

We are running an instance of cockpit as part of a microservices architecture in a kubernetes cluster.

We’d like to get rid of the state in the local file system to ease up the management of our system, so we configured cockpit to use mongodb.

Unfortunately, cockpit cms still uses the local file system to store uploaded images and metadata of the collections. So we end up to have the state of cockpit cms split up in two places.

Are there plans for future versions to improve this. Technically it shouldn’t be too complicated to store the metadata of the collections and the uploads in mongodb too. Unfortunately, we don’t have any PHP-developers, so we can’t contribute.

You can use the CloudStorage addon:
to save you assets on S3, azure etc.