Skip to content

Storage Backends

Jennings Zhang edited this page Jun 5, 2023 · 2 revisions

CUBE supports two storage backends, which is configured by the setting DEFAULT_FILE_STORAGE.

See ChRIS backend production services secret configuration files for how to configure CUBE using environment variables.

Supported Storage Backends

Name Configuration Description Recommendation
OpenStack Swift swift.storage.SwiftStorage OpenStack Swift is a distributed object storage service Suitable for multi-user systems, cloud, where reliability and concurrency matter
Filesystem storage django.core.files.storage.FileSystemStorage Stores files in a directory on the host. Uses hard-links to efficiently store duplicated files. Filesystem storage is simple and preferable for single-machine, single-replica deployments

Specific Configuration

OpenStack Swift

SWIFT_CONTAINER_NAME=users
SWIFT_AUTH_URL=http://swift:8080/auth/v1.0
SWIFT_USERNAME=chris:chris1234
SWIFT_KEY=testing

Filesystem Storage

MEDIA_ROOT=/var/chris

MEDIA_ROOT is the path on the filesystem where CUBE stores file data. The same volume must be mounted to MEDIA_ROOT for all of CUBE's components (server and 2 celery workers)

Clone this wiki locally