distroless has no shell, so managing packages against a running
container means exec-ing the ccc binary directly. Files being added
need to exist inside the container already, so bind-mount a host
./staging dir to /staging for that.
- docker-compose.yml: mount ./staging:/staging alongside the data volume
- README: document docker compose exec + staging workflow
Multi-stage build: rust:1-slim-bookworm to compile (needs a recent
toolchain per smarm/urus's MSRV), then a distroless/cc runtime image
since the binary only links against glibc/libgcc/libm (checked via
ldd) - no shell or package manager needed at runtime, ~27MB vs ~87MB
for a debian-slim runtime.
- CCC_DB_PATH defaults to /data/cdn.db in-container
- docker-compose.yml persists /data in a named volume, maps 8333
A minimal CDN for serving versioned, gzip-compressed static assets,
backed by SQLite and an actor-based (smarm) storage server, with
HTTP serving via urus.
- CLI: create/add/archive packages and versions, serve over HTTP
- Storage: SQLite-backed asset store (src/store.rs) with gzip
compression on ingest and content-type sniffing by extension
- HTTP: GET /packages (list packages+versions), GET
/assets/:package/:version/:filename (serves gzip or transparently
decompressed, with immutable long-lived cache headers)
Markk116