Repository navigation
Code MinIO
The local and CI MinIO image is built from official source commits. The former Quay and Docker Hub images refuse anonymous pulls, and the historical binary download endpoints return HTTP 410. No third-party binary mirror is used.
| Binary | Existing release | Source commit |
|---|---|---|
| MinIO | RELEASE.2025-09-07T16-13-09Z |
07c3a429bfed433e49018cb0f78a52145d4bedeb |
| mc | RELEASE.2025-08-13T08-35-41Z |
7394ce0dd2a80935aded936b09fa12cbb3cb8096 |
docker compose build minio builds both binaries sequentially with two Go
threads, one compiler process, and a 512 MiB Go memory target. BuildKit caches
modules and compilation on Docker's disk. The first build needs network access
and takes longer than pulling the former image; subsequent builds reuse it.
make up builds the image before starting the stack. Both services share the image,
and scripts/verify-r2.sh uses its client too.
CI does not repeat that build on every run. .github/workflows/minio-image.yml
publishes the image to ghcr.io/<owner>/quizzivy-minio, a public package as
the repository is, under a tag that is a hash of this directory, and
.github/actions/minio pulls it. A change here, this file included, names a
new tag, which CI builds from source until it is published. The image's labels
name the licence (AGPL-3.0-or-later) and this repository, where the table
above lists the unmodified source commits.
The image contains the upstream license and credits for each binary. It is a
development/CI stand-in for production Cloudflare R2; these historical releases
are not a supported production storage deployment. Changing this image does not
remove the local minio-data volume.
Generated from docker/minio/README.md. Edit that file in the repository; changes made on this page are overwritten.
Generated from the repository's documentation on every push to develop.
Start here
Product
Implementation plan
- 00 Architecture overview
- 10 Phase 0: Scaffold and contract
- 11 Phase 1: Auth, join, shells
- 12 Phase 2: Admin authoring
- 13 Phase 3: Assign and take
- 14 Phase 4: Grade and results
- 15 Phase 5: Hardening
- 16 Phase 4.5: The student at a desk
- 17 Word import: milestone plan
- 18 Word import: teacher workflow
- 19 Versioned content contract
- 20 Data model
- 30 Risk register
- 40 Open items
- 50 Non-functional requirements
- 60 Backend architecture
- 91 September 2026 issue remediation
- 92 Student layouts and interaction rules
Redesign (Phase R)
- 70 Redesign overview
- 71 R1: Foundations (v0.7.0)
- 72 R2: Access (v0.8.0)
- 73 R3: Student console (v0.9.0)
- 74 R4: Teacher workspace (v0.10.0)
- 74d D4: Deck update (v0.11.0)
- 74e E1: Moving a question across a group
- 75 R5: Admin console and email (v0.12.0)
- 76 R6: Question types and scoring (v0.13.0)
- 77 R7: Collaboration (v0.14.0)
- 78 R8: Schedule (v0.15.0)
- 79 R9: Insights (v0.16.0)
- 80 R10: Learn (v0.17.0)
- 81 R11: Landing, leads, v1.0 (v1.0.0)
Setup and operations
- CI
- Deploying
- DNS for quizzivy.com
- Google OAuth client
- Production operations
- Cloudflare R2 bucket
- Word import worker
- R4 rehearsal on a Neon branch
Design
Team
- Agent team
- Verification environment
- Team ledger
- R4 readiness
- R4 verification strategy
- T-R4.51 browser verification
Code READMEs