cabbage/kosync-rs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use published Docker image in defaults

Browse Source
This commit is contained in:
Codex
2026-06-12 14:32:52 +00:00
parent c1f568be1d
commit aab4764e48
4 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -14,7 +14,7 @@ Compatibility target:
## Quick start
```sh
docker compose up -d --build
docker compose up -d
curl -k -H "Accept: application/vnd.koreader.v1+json" https://127.0.0.1:7200/healthcheck
```
@@ -22,6 +22,9 @@ The compose file stores data in `./data/kosync.sqlite3`, enables user
registration, exposes HTTPS on `7200`, and exposes plain HTTP on `17200` for
reverse proxies.
The default compose file uses the published multi-arch image
`sodium/kosync-rs:v2.1.1`, which supports Linux `amd64` and `aarch64`.
## Binary usage
```sh
@@ -78,7 +81,7 @@ container's network namespace.
scripts/import-from-old-redis.sh \
--old-container kosync \
--sqlite ./data/kosync.sqlite3 \
--image kosync-rs:latest
--image sodium/kosync-rs:v2.1.1
```
Then stop the old container and start the new compose stack:
@@ -94,7 +97,7 @@ Export SQLite data back to the old Redis format:
scripts/export-to-old-redis.sh \
--old-container kosync \
--sqlite ./data/kosync.sqlite3 \
--image kosync-rs:latest
--image sodium/kosync-rs:v2.1.1
```
The export script will not flush Redis unless `--flush-target` is passed.