This guide covers the packaging and shipping paths that are current today.
| Artifact | Command | Notes |
|---|---|---|
| source install | cargo install --path . |
installs full CLI toolchain |
| release archive | bash scripts/create-release-archive.sh --version 1.0.2 |
packages sqlrite |
| release installer | bash scripts/sqlrite-install.sh --version 1.0.2 |
installs sqlrite |
| Docker image | docker build -t sqlrite:local . |
service deployment baseline |
| seeded Docker Compose demo | docker compose -f deploy/docker-compose.seeded-demo.yml up --build |
seeded local demo server |
bash scripts/create-release-archive.sh --version 1.0.2Outputs:
dist/sqlrite-v1.0.2-<target>.tar.gzdist/sqlrite-v1.0.2-<target>.sha256
When nfpm is installed:
bash scripts/package-linux.sh --version 1.0.2docker build -t sqlrite:local .
docker run --rm -p 8099:8099 -v "$PWD/docker-data:/data" sqlrite:localContainer behavior:
| Behavior | Result |
|---|---|
| database path | /data/sqlrite.db |
| empty mounted directory | SQLRite creates an empty schema-applied database |
| default command | sqlrite serve --db /data/sqlrite.db --bind 0.0.0.0:8099 |
If you want a ready-to-query container immediately:
mkdir -p docker-data
sqlrite init --db ./docker-data/sqlrite.db --seed-demo
docker run --rm -p 8099:8099 -v "$PWD/docker-data:/data" sqlrite:localdocker compose -f deploy/docker-compose.seeded-demo.yml up --buildThis flow:
- seeds the database once if the volume is empty
- starts the HTTP server on
8099 - keeps the database in a named volume