How deadrop-dev/server works
Deadrop Server is a self-hostable HTTP service for zero-knowledge secret sharing. A client submits opaque encrypted secrets, and retrieval verifies a key hash before atomically burning the stored record; the reverse Request-a-Secret flow lets a responder attach an encrypted reply for a proof-bearing claimant. Runtime setup loads configuration and selects storage before serving the API. The excerpts show routing, validation, middleware, rate limiting, persistence, and cleanup; some request-flow and SQLite details are only partially excerpted, so the graph avoids unshown internal call sequences.
Main entry points: main.go Server process · server.go HTTP routing · requests.go Request endpoints · storage.go Store interface
Components 16
Runtime setup
- Configuration loader
internal/config/config.go - Server process
cmd/deadrop-server/main.go
HTTP API
- HTTP routing
internal/server/server.go - Secret endpoints
internal/server/handlers.go - Request endpoints
internal/server/requests.go - Wire validation
internal/server/validate.go
Request controls
- HTTP middleware
internal/server/middleware.go - Rate limiter
internal/ratelimit/ratelimit.go - Metrics
internal/server/metrics.go
Persistence
- Store interface
internal/storage/storage.go - SQLite store
internal/storage/sqlite.go - Memory store
internal/storage/memory.go
Other components
- Deadrop client
- Operator config
- Secret requester
- Secret responder
Connections 20
- Operator config → Configuration loader: provides settings
internal/config/config.go - Server process → Configuration loader: loads settings
cmd/deadrop-server/main.go - Server process → SQLite store: opens by default
cmd/deadrop-server/main.go - Server process → Memory store: selects optionally
cmd/deadrop-server/main.go - Server process → HTTP routing: constructs and serves
cmd/deadrop-server/main.go - Deadrop client → HTTP routing: sends API requests
README.md - Secret requester → Request endpoints: creates and claims
README.md - Secret responder → Request endpoints: checks and fulfills
README.md - HTTP routing → Secret endpoints: routes secret calls
internal/server/server.go - HTTP routing → Request endpoints: routes request calls
internal/server/server.go - HTTP routing → HTTP middleware: wraps handlers
internal/server/server.go - Secret endpoints → Wire validation: validates payloads
internal/server/handlers.go - Request endpoints → Wire validation: validates payloads
internal/server/requests.go - Secret endpoints → Store interface: reads and burns secrets
internal/server/handlers.go - Request endpoints → Store interface: stores and claims requests
internal/server/requests.go - HTTP middleware → Rate limiter: checks request limits
internal/server/middleware.go - HTTP middleware → Metrics: records request metrics
internal/server/middleware.go - Store interface → SQLite store: implemented by
internal/storage/storage.go - Store interface → Memory store: implemented by
internal/storage/storage.go - Server process → Store interface: runs expiry cleanup