Files
Calibre-Web-Automated/docker-compose.yml.dev
T

33 lines
2.0 KiB
Plaintext

---
services:
calibre-web-automated:
image: crocodilestick/calibre-web-automated:latest
container_name: calibre-web-automated
environment:
# Only change these if you know what you're doing
- PUID=1000
- PGID=1000
# Edit to match your current timezone https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
- TZ=UTC
# Hardcover API Key required for Hardcover as a Metadata Provider, get one here: https://docs.hardcover.app/api/getting-started/
- HARDCOVER_TOKEN=your_hardcover_api_key_here
volumes:
# CW users migrating should stop their existing CW instance, make a copy of the config folder, and bind that here to carry over all of their user settings ect.
- /path/to/config/folder:/config
# This is an ingest dir, NOT a library one. Anything added here will be automatically added to your library according to the settings you have configured in CWA Settings page. All files placed here are REMOVED AFTER PROCESSING
- /path/to/the/folder/you/want/to/use/for/book/ingest:/cwa-book-ingest
# If you don't have an existing library, CWA will automatically create one at the bind provided here
- /path/to/your/calibre/library:/calibre-library
# If you use calibre plugins, you can bind your plugins folder here to have CWA attempt to add them to it's workflow (WIP)
- /path/to/your/calibre/plugins/folder:/config/.config/calibre/plugins
# DEV SPECIFIC BINDS
### The current easiest way to develop CWA is to live edit a running instance.
### To do so, use docker binds to bind the files your working on to their counterparts in the running container.
### This will let you see your changes in realtime, test ect. You can use build.sh to prepare images with your changes.
# /your/dev/env/file:/location/of/the/file/in/the/container_name
ports:
# Change the first number to change the port you want to access the Web UI, not the second
- 8083:8083
restart: unless-stopped