View Single Post
Old 07-24-2023, 06:58 AM   #7
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by boox View Post
Is it only me or does the KOreader progress sync fail for you too since yesterday?

I ask again: Is there any other sync server available I may use to avoid the KOreader sync server outages?

Is there any other possibility to sync progress instead using a full blown Docker install?

I am thinking of synching by running a PHP (commonly available) script on a webspace. E.g. provide a JSON file to the webspace or get it from there. This would be a light synching variant.
Have a look at https://github.com/topics/koreader-sync

You can find more alternatives on github et al, like:

https://github.com/jberlyn/kosync-dotnet
https://github.com/dobladov/koreader-node-sync-server
https://github.com/relkochta/koreader-sync

All of these are usually easier to deploy and are focused on single/few users.
pazos is offline   Reply With Quote