mirrors/calibre-web
1
0
Fork 0
mirror of https://github.com/janeczku/calibre-web synced 2024-12-13 11:40:30 +00:00
Code Issues Releases Wiki Activity

Added section for multiple files

Ozzieisaacs 2019-06-06 20:16:49 +02:00
parent 54747bb49d
commit db949c5530
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
FAQ.md

@ -124,6 +124,18 @@ The read/unread status is now identical in Calibre and Calibre-Web
### How to handle Multiple calibre-libs
The recommended way for handling mulitple libraries is to start multiple instances of calibre-web. Instead of having several copies of the calibre-web code, command line options can be used for this. First start calibre-web with the normal command:\
`python3 [path to calibre-web]/cps.py`
Configure the path to the metadata.db, set the logfile to a new filename (e.g. instance1.log) and change the port to e.g. 8084. Now stop calibre-web rename the newly generated app.db to e.g. instance1.db. Repeat this procedure for every instance you want to run. At the end start all instance with the commandline-parameter -p:\
```
nohup python3 [path to calibre-web]cps.py -p /[path to calibre-web]instance1.db
nohup python3 [path to calibre-web]cps.py -p /[path to calibre-web]instance2.db
...
nohup python3 [path to calibre-web]cps.py -p /[path to calibre-web]instanceN.db
```
The command nohup puts the command to the background, so all instances can be started at once. Another option would be using several terminal windows. The final solution would be creating different service files for the different instances. All instances will be accessable afterwards with different port adresses like:\
127.0.0.1:8084 for instance1, 127.0.0.1:8085 for instance2 and so on. This procedure can also be used for windows with the usual adoptions (command console/batch programm instead of terminal, task planer instead of service script).
### Registering