Makepad MinIO

Shared MinIO deployment for Makepad-fr applications.

This repository owns the shared MinIO server that application repositories connect to over app-specific external overlay networks. Application repositories should not deploy MinIO directly in canary or production.

Layout

• compose.yml: base MinIO service definition
• envs/canary/compose.yml: canary Swarm overrides
• envs/canary/.env.minio: canary MinIO settings
• envs/production/compose.yml: production Swarm overrides
• envs/production/.env.minio: production MinIO settings

Networks

The shared MinIO service joins app-specific external overlay networks. For Catwlk:

• ${DEPLOY_CATWLK_OBJECTS_NETWORK}

Application stacks attach to the same network and connect to the stable service alias makepad-minio.

Buckets

Use one bucket per application. For Catwlk:

• canary: ${MAKEPAD_MINIO_CATWLK_BUCKET}
• production: ${MAKEPAD_MINIO_CATWLK_BUCKET}

Applications should use their own bucket instead of sharing a global one.

Node Labels

Pin the shared MinIO server to the database/storage node:

docker node update --label-add infra.makepad.minio=true <db-node>

That label can coexist with infra.makepad.postgres=true on the same VM.

Deployment

Use the manual GitHub Actions workflow in this repository.

Required environment secrets:

• DEPLOY_SSH_HOST
• DEPLOY_SSH_PORT
• DEPLOY_SSH_USER
• DEPLOY_SSH_PRIVATE_KEY
• DEPLOY_REMOTE_DIR
• DEPLOY_STACK_NAME
• DEPLOY_CATWLK_OBJECTS_NETWORK

The workflow deploys only the MinIO stack. If the Catwlk objects network does not exist yet, it is created on the manager before deployment. It also ensures the Catwlk bucket exists after the service is updated.