1
0
mirror of https://github.com/ciromattia/kcc synced 2026-01-28 07:57:41 +00:00

Outlining relative paths for Docker usage

pjft
2024-09-29 10:20:39 +01:00
parent b7270bb272
commit 2be24eef7b

@@ -124,7 +124,8 @@ flatpak run --command=kcc-c2e io.github.ciromattia.kcc "$@"
### DOCKER
install kindlegen in your working directory and get last docker image
Install kindlegen in your working directory (the folder you're going to run KCC from) and get last docker image.
```bash
$ docker pull ghcr.io/ciromattia/kcc:latest
```
@@ -144,6 +145,15 @@ execute kcc-c2p
$ docker run --entrypoint /opt/kcc/kcc-c2p.py --rm -v "$(pwd):/app" ghcr.io/ciromattia/kcc:latest
```
Regarding local paths, the Docker container will only have access to the current folder and subfolders from where you're running it from. If you need to run this for relative paths, it gets trickier but is certainly doable.
Kindlegen **must be accessible to the Docker container in its /app folder**. You must also make your other path accessible in another folder. Here's one such example, if you want to convert `1.cbz` in your local `/path/to/sourcefiles` folder:
```bash
$ docker run --rm -v "/path/to/kindlegen:/app" -v "/path/to/sourcefiles:/app/files" ghcr.io/ciromattia/kcc:latest -p KPW5 files/1.cbz
```
where `/path/to/kindlegen` is the folder where you have Kindlegen in, and `/path/to/sourcefiles` is the path to the source files you're trying to convert.
## INSTALL FROM SOURCE