Hi folks,
Calibre2opds uses relative links, which means that the URLs generated by a cloud-sync system (e.g. Dropbox) must be consistent.
Here's an example : let's imagine that I have a folder A with two subfolders, A1 and A2. In A1 I've got a file named F1, and in A2 I've got F2 and F3...
In the Dropbox
public folder (this is important), if the URL of A is
http://dl.dropbox.com/u/343343/A, then the URL of F1 is
http://dl.dropbox.com/u/343343/A/A1/F1 and the URL of F3 is
http://dl.dropbox.com/u/343343/A/A2/F3
Now, in a Dropbox private folder, things are different. If for example the URL of A is
http://dl.dropbox.com/u/343343/p/ZERZERF/A, then calibre2opds will deduct that the URL of F1 is
http://dl.dropbox.com/u/343343/p/ZERZERF/A/A1/F1 ; in this case, it will be different (for example
http://dl.dropbox.com/u/343343/p/RGERRE/F1), and calibre2opds will not work.
To sum it up, on cloud-sync systems where this remains true, calibre2opds will work. On other systems, which obfuscate the URLs one way or another, it will not.
Hope this clears the question...
David.