Local Development Still Requires Real AWS S3 Credentials — MinIO Not Used Despite PR #1738

[Treata11]

Although PR #1738 introduced MinIO support for the test environment, local development (rails server) still depends on real AWS S3 credentials to function correctly.

This blocks contributors from testing features locally without paid AWS access.

Details

As configured in #1738,.env.test does use MinIO:

env envAWS_S3_ENDPOINT=http://localhost:9000 
AWS_ACCESS_KEY_ID=minioadmin 
AWS_SECRET_ACCESS_KEY=minioadmin

Whereas .env.development doesn't:

  S3_DELETER_ACCESS_KEY_ID="<set me>"
  S3_DELETER_SECRET_ACCESS_KEY="<set me>"
  AWS_ACCESS_KEY_ID=dummy_key

.env.development lacks any AWS_S3_ENDPOINT or MinIO configuration. The README still instructs users to create real S3 buckets.

This is a known pain point: see Issue 253, #1774 ...

Suggestion

Extend MinIO support to the development environment by:

• Adding AWS_S3_ENDPOINT, AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY defaults to .env.development
• Optionally bundling a lightweight MinIO service in docker-compose.yml for local runs
• Updating the README with clear setup instructions for MinIO-based local S3 emulation

[slavingia]

@ershad wdyt?

[slavingia]

@ershad is working on this

[ershad]

We are working on that here: https://github.com/antiwork/gumroad/pull/1773

@Treata11 there are some spec failures, please feel free to send PRs to that branch if you would like.