Server commands, storage, authentication, and production boundaries.
Operating the registry
Server and token commands
dvlib-server run --data-dir /srv/dvlib --host 127.0.0.1 --port 8000
dvlib-server tokens create --label ci-publisher --data-dir /srv/dvlib
dvlib-server tokens list --data-dir /srv/dvlib
dvlib-server tokens revoke --data-dir /srv/dvlib
Storage model
The data directory contains registry.db and packages/<name>/<version>.tar.gz. SQLite is a single-writer store suited to modest private registries; a concurrent publish workload may require a different database design.
Read and write boundaries
- Package reads are open to clients that can reach the service.
- Publish and yank require a bearer token; the registry stores token hashes, not raw tokens.
- Client credentials live in ~/.config/dvlib/credentials.toml unless DVLIB_TOKEN is supplied.
Before production exposure
- 1 Terminate TLS at a reverse proxy and use an https registry URL.
- 2 Restrict network reachability to the intended engineering environment.
- 3 Back up registry.db and packages/ as one consistent unit.
- 4 Treat published archives as untrusted input; the built-in service has no malware scanning or quotas.