1
0
mirror of https://github.com/janeczku/calibre-web synced 2025-07-05 11:32:57 +00:00

Added backup

Ozzie Isaacs 2020-01-24 12:09:59 +01:00
parent f223e1060f
commit 60243f7a18

3
FAQ.md

@ -140,6 +140,9 @@ 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:\ 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). 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).
### How to backup Calibre-Web settings
All Calibre-Web data is stored in the app.db file. For google drive additional settings are stored in the gdrive.db, settings.yaml, gdrive_credentials and client_secrets.json. It's sufficent to backup this files to keep the settings. The calibre database has to be backuped seperatly.
### Registering ### Registering