Connecting Nextcloud, Calibre-Web and External Storage

HelenaGwyn there is a newer version of sqlite available in /usr/sqlite330/bin/so try running export PATH=/usr/sqlite330/bin/:$PATH then repeat whatever it is you were attempting to do.

HelenaGwyn where exactly do you see the error message?

HelenaGwyn ok, please try this:

1. Activate your app's environment.
2. Install pysqlite3-binary: pip3 install pysqlite3-binary
3. Edit env/bin/cps to add the following lines just after import sys:
   
   

   __import__('pysqlite3')
   sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')

4. Deactivate the environment and then re-activate it.
5. Stop the running cps process and restart it.

HelenaGwyn Nice, I honestly wasn't sure if that would work!

Note that you'll need to make that last change again if you ever update the calibreweb Python package.

Eventually we'll have an updated OS with newer software so that things like these sqlite3 gymnastics won't be necessary

HelenaGwyn I don't think nextcloudcmd would help with this. That tool syncs from a Nextcloud instance to a client directory, but it doesn't sync files between 2 Nextcloud instances, which I think is what you want to do?

If you use rclone (or any other external sync tool) to sync files directly into the Nextcloud filesystem, ie into ~/apps/nextcloud/data/username/files then you'll need to tell Nextcloud to sync up its database after the file sync is complete. The commands to do that are:

cd ~/apps/nextcloud
php74 occ files:scan --all

So you'd need to incorporate that into whatever cron job you run for your sync.

HelenaGwyn in that case I think you should be able to use any sync tool (rclone, rsync, whatever) to sync the Calibre library directories on each end.

HelenaGwyn yes, you should be able to use rclone mount.

HelenaGwyn I think you'll need to combine both, ie you'll need to run a separate instance of calibreweb for each library and then wire them all up to a private Nginx instance.

For each additional instance of calibreweb you'll need to create a new "Nginx Proxy Port" app and then start a new instance of the existing cps script listening on the new port assignment and pointing at a new database, eg:

# replace NNNNN with your port assignment
export CALIBRE_PORT=NNNNN 
# replace XXXXX with the library name
( nohup ~/apps/name_of_app/env/bin/cps -i 127.0.0.1 -p $HOME/.calibre-web/XXXXX-app.db -g $HOME/.calibre-web/XXXXX-gdrive.db >> ~/logs/apps/name_of_app/name_of_app.log 2>&1 & )

Then in your Nginx instance config, each Calibreweb instance will get a location block like so:

    # replace XXXXX and NNNNN with your library name and port assignment as above.
    location /XXXXX {
        proxy_pass http://127.0.0.1:NNNNN;
        proxy_set_header Host $http_host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $server_name;
        proxy_set_header X-Scheme $scheme;
        proxy_set_header X-Script-Name /XXXXX;
    }

HelenaGwyn So I assume that just means leaving out the -g variable and configuring the database)location during the setup of the instance itself.

In my testing Calibreweb created a gdrive database whether I told it to or not. If you run into problems without specifying the path then go ahead and include it as I've shown.

HelenaGwyn Is $HOME/.calibreweb/<library_name> the best location to mount my database-folders?

$HOME/.calibre-web is the default location that Calibreweb sets up, you're free to change it if you like.

HelenaGwyn the 'deleting' seems to be stuck. I assume that's something you have resolve?

Yep, something was stuck on our end. All clear now!

HelenaGwyn Ok, please email support with the details and someone on our team will have a look.