Quote:
Originally Posted by Starson17
Can you enlighten on me on the differences between running calibre2opds made available via Apache versus running the Calibre content server and its integrated /opds access?
|
(itimpi, hope you don't mind me taking this)
calibre2opds generates a slew of static HTML pages. If you copy them into Apache's document space somewhere, then poof, you have a web site. There are no programs required other than apache. You get apache's multithreading, url rewriting, virtual hosting, etc. You can use SSL. I use calibre2opds, and use dropbox to move the pages automatically when I regenerate them. One reason I do this is that I don't want to take the trouble of installing calibre on my production web server (distro too old).
Calibre's content server is active. You must install it, with all its dependencies, and then run it and maintain it. The library must be visible to it, or probably copied to it. It uses memory, which might be precious on the server (I often run on servers with 512kb total ram). It wants to talk HTTP over TCP, meaning that anything in front of it must act like a client. It doesn't support SSL (authentication is visible) or password-per-user. However, it does give up-to-date answers, which is a very good thing.
To run calibre's content server in a single web space with other web servers (one name, one port), you must set up a 'reverse proxy' that knows where to direct the network packets, and knows how to munge them on the way back. I know how to do this with squid (have done), and today learned that apache can also do it. This doesn't solve the other problems such as old distros, but it is a good step forward.