Object Storage on

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

By default, Relution stores certain resources - such as native app binaries - in its database. This can cause the resource table to grow very large, especially when managing many native apps.

To optimize performance, Relution supports storing these resources in external S3-compatible object storage buckets.

⚠️ MinIO Users: MinIO ceased development in October 2025 and will not receive updates. We recommend migrating to SeaweedFS using our guide: Object Storage Migration →

SeaweedFS Setup

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

SeaweedFS is an Apache-licensed open-source object storage backend with an S3-compatible API. It offers good performance, scalability, and an easy setup process. It can be deployed via Kubernetes, Docker, or directly on Linux, FreeBSD, macOS, or Windows.

This guide explains how to deploy SeaweedFS alongside Relution using Docker Compose on Linux.

While we have thoroughly tested it, SeaweedFS is third-party software and we cannot make security or reliability guarantees for it.
For managed hosting, please contact our Sales Team.
More info: Relution Cloud →

Configure Relution

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Once you have an S3-compatible object storage backend ready - whether self-hosted or cloud-based - you need to configure Relution to use it.

Prerequisites

You’ll need the following information from your object storage provider:

Setting	Description
Endpoint	The S3 API URL
Access Key	Authentication key ID
Secret Key	Authentication secret
Bucket Name	The storage bucket name

In the configuration examples below, we will use example values matching our SeaweedFS guide. If you are using a different backend or provider, adjust them accordingly.

Migration Guide

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

This guide explains how to migrate your Relution data from one object storage backend to another. Common scenarios include:

Migrating from MinIO to SeaweedFS (MinIO is no longer maintained)
Moving from cloud provider to self-hosted (or vice versa)
Switching cloud providers

The examples below demonstrate a migration from MinIO to SeaweedFS, but the steps can be adapted for any S3-compatible source and destination.

Overview

The migration process consists of four steps:

Deprecated: MinIO

Mon, 01 Jan 0001 00:00:00 +0000

Important Notice

⚠️ Important: > MinIO has discontinued further development without prior notice in October 2025. We therefore discourage the further usage of MinIO.

You can find our new info on object storage here: Object Storage →
To migrate away from MinIO, we have created a guide: Migration →

Deprecated MinIO Setup Instructions

Introduction

minIO is a scalable, object-based storage solution with high performance. In Relution, the resource table can grow very large (e.g., due to stored native apps). To relieve the database, it is recommended to outsource these app files into an S3 bucket.

Object Storage on

Overview

Introduction #

SeaweedFS Setup

Introduction #

Configure Relution

Introduction #

Prerequisites #

Migration Guide

Introduction #

Overview #

Deprecated: MinIO

Important Notice #

Introduction #

Introduction

Introduction

Introduction

Prerequisites

Introduction

Overview

Important Notice

Introduction