Object storage with Minio

Min.io is a "High Performance Object Storage". If you want to keep store your (uploaded) files

You can extend Corteza docker-compose.yaml, create additional deployment (see example) or use existing Min.io services

Extending your docker-compose.yaml file:

service:
  # ... other services
  minio:
    # env_file: [ .env ] (1)
    image: minio/minio
    networks: [ internal ] (2)
    restart: on-failure
    volumes: [ "minio-data:/data" ]
    command: server /data
    ports: [ "9000:9000" ]
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

volumes: { minio-data: {} }

1	Uncomment if you want to use `MINIO_*_KEY` values from `.env`.
2	This example assumes that Min.io is on a private (internal) network and can (should) not be reached form the outside

Extend .env file and point Corteza to Min.io instance:

# Storage to minio backend is activated when MINIO_ENDPOINT is set
MINIO_ENDPOINT=minio:9000

# Access & secret key
MINIO_ACCESS_KEY=<to-be-configured> (1)
MINIO_SECRET_KEY=<to-be-configured> (1)

1	Use exiting access & secret keys or generate new