You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started Libation on macOS then saw there's an unsupported docker option. I did not finish downloading to leave some for testing with docker.
I'd prefer to run this in docker so I don't have to rely on manually opening Libation on an endpoint and have a question.
If I copy AccountsSettings.json, Settings.json, and LibationContext.db to the respective volumes, is this all that is needed to "resume" downloading from the stopping point on the macOS endpoint?
The goal is to avoid redownloading from the start again and potentially creating duplicates and having to deal with cleanup.
If it helps, below is my docker compose draft:
services:
libation:
container_name: libation
restart: unless-stopped
image: rmcrackan/libation:latest
user: 1000:1000
volumes:
- /opt/docker/config/libation:/config
- /opt/docker/config/libation/db:/db
- /mnt/Audiobooks:/data
environment:
- SLEEP_TIME=12h #Length of time to sleep before doing another scan/download. Set to -1 to run one.
- LIBATION_BOOKS_DIR=/data #Folder where books will be saved
- LIBATION_DB_DIR=/db #Optional folder to load database from. If not mounted, will load database from LIBATION_CONFIG_DIR.
- LIBATION_DB_FILE=LibationContext.db #Name of database file to load. By default it will look for all .db files and load one if there is only one present.
The text was updated successfully, but these errors were encountered:
Thank you, worked perfectly minus a typo on my end.
A couple of follow up questions:
The Breaking Changes for Docker mention InProgress value in Settings.json. Mine doesn't have a InProgress value, not that it matters since it's ignored anyway, but per the container logs there is a /tmp directory being used. Does it need to be a volume mount or is container-side sufficient? It seems to be working just fine as is but wanted to confirm. Logs below for reference.
2025-02-08 00:27:35 info: initializing libation
2025-02-08 00:27:35 info: loading AccountsSettings.json
2025-02-08 00:27:35 info: loading Settings.json
2025-02-08 00:27:35 info: loading settings
2025-02-08 00:27:35 info: setting Books to /data
2025-02-08 00:27:35 info: setting InProgress to /tmp
2025-02-08 00:27:35 info: loading database
2025-02-08 00:27:35 info: database found at /db/LibationContext.db
2025-02-08 00:27:35 info: running every '12h'
2025-02-08 00:27:35 info: scanning accounts
Scanning Audible library. This may take a few minutes.
Scan complete.
Total processed: 412
New: 0
2025-02-08 00:27:40 info: liberating books
...
How can we get a compose sample added to the Docker doc page?
How can we get a compose sample added to the Docker doc page?
If you know how to do PRs, you're also welcome to submit one directly. If that sentence made no sense to you or if you're not comfortable doing PRs: After this issue is resolved, finish by "at"-ing me in your last message here, and lemme know what to put on that doc page.
I started Libation on macOS then saw there's an unsupported docker option. I did not finish downloading to leave some for testing with docker.
I'd prefer to run this in docker so I don't have to rely on manually opening Libation on an endpoint and have a question.
AccountsSettings.json
,Settings.json
, andLibationContext.db
to the respective volumes, is this all that is needed to "resume" downloading from the stopping point on the macOS endpoint?The goal is to avoid redownloading from the start again and potentially creating duplicates and having to deal with cleanup.
If it helps, below is my docker compose draft:
The text was updated successfully, but these errors were encountered: