Local Development

This guide walks through setting up a full local development environment with MinIO as the backing object store.

Docker Compose

The project includes a docker-compose.yaml that starts MinIO and seeds it with example data:

docker compose up

This starts:

• MinIO API at http://localhost:9000
• MinIO Console at http://localhost:9001 (credentials: minioadmin / minioadmin)
• A seed job that creates public-data and private-uploads buckets with sample files

Configuration Files

The two runtimes use different config formats:

Workers Runtime — examples/cf-workers/wrangler.toml

The CF Workers runtime reads PROXY_CONFIG from the Wrangler configuration. The shipped wrangler.toml points the public-data and private-uploads buckets at http://localhost:9000 (the MinIO instance seeded by Docker Compose), so it works against the local backend out of the box:

cd examples/cf-workers && npx wrangler dev

The Workers dev server runs on port 8787 by default. This is the recommended runtime for the local MinIO quickstart.

Server Runtime — examples/server/config.toml

The server runtime reads a TOML config file, defaulting to config.toml in the working directory. The shipped examples/server/config.toml serves the harvard-lil and cholmes buckets from real AWS S3 (not the local MinIO buckets), so point --config at your own config to use a local backend:

cargo run -p multistore-server -- \
  --config examples/server/config.toml \
  --listen 0.0.0.0:8080

Building

# Check/build default workspace members (excludes cf-workers)
cargo check
cargo build

# CF Workers must target wasm32
cargo check -p multistore-cf-workers --target wasm32-unknown-unknown

# Run tests
cargo test

Environment Variables

For local development, these are optional but useful:

Variable	Purpose	Example
SESSION_TOKEN_KEY	AES-256-GCM key for sealed tokens	openssl rand -base64 32
OIDC_PROVIDER_KEY	RSA private key for OIDC backend auth	PEM file contents
OIDC_PROVIDER_ISSUER	Public URL for OIDC discovery	http://localhost:8080
RUST_LOG	Logging level	multistore=debug

Verifying the Setup

Once the Workers dev server is running, test both anonymous and authenticated access against the local MinIO buckets:

# Anonymous read (should return file contents)
curl http://localhost:8787/public-data/hello.txt

# Authenticated upload
AWS_ACCESS_KEY_ID=AKLOCAL0000000000001 \
AWS_SECRET_ACCESS_KEY="localdev/secret/key/00000000000000000000" \
aws s3 cp ./test.txt s3://private-uploads/test.txt \
    --endpoint-url http://localhost:8787

# List bucket contents
AWS_ACCESS_KEY_ID=AKLOCAL0000000000001 \
AWS_SECRET_ACCESS_KEY="localdev/secret/key/00000000000000000000" \
aws s3 ls s3://private-uploads/ \
    --endpoint-url http://localhost:8787

# Browse MinIO directly
open http://localhost:9001