S3 API (self-hosted) support
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 3
- Avg merge
- 21m
- Merged PRs (30d)
- 3
Description
Currently production serves media over NFS. Let's add S3 API support to eventually replace it. By S3 API we mean self-hosted GarageFS.
* Stage 1: introduce S3 API storage option, store new uploads in it (direct presigned url if reasonably possible), serve media from it (again presigned urls if reasonably possible)
* [ ] Blocked by QB GarageFS rollout
Stage 2: migrate legacy media to GarageFS and scrap the NFS mount in production, keeping the file system storage option as a discouraged alternative. Remove the nginx container altogether.
References #241: If media is in GarageFS, it is only ever accessed via authenticated S3 API access (either per-request SigV4 or pre-signed URL). This cleanly resolves the unauthorized media access problem.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named in the issue. Start by tracing the existing NFS/file-system media storage path and the production nginx configuration, then review the GarageFS rollout dependency. Done means Stage 1 supports authenticated S3 access for new uploads and media serving; migration and NFS removal are listed as a later stage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, nginx, postgresql, typescript
- Domain
- backend, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100