Please note that this is a work in progress. Changes – even API breaking changes – might happen at any time.
I love books. Always have. Since I was a kid. Over the years several thousand books gathered in my flat; so many that I sort of ran out of space. Reluctantly I started to investigate and then use eBooks, first on my main desktop computer, later with a dedicated eBook reader.
Soon – and again – there were so many that I started looking for some convenient way to handle, store, and retrieve them for reading. That's when I became acquainted with Calibre, a great software for working with eBooks. Of course, there were some problems but since that software is actively maintained and extended all the time those problems either went away on their own with the next update or I found some way around them. And sure, it took some work to get all the eBooks into that library system, and since there are always coming new titles the work kind of never ends.
Another question soon became urgent: How to access my books when I'm not at home?
As it turned out, Calibre comes bundled with its own web-server.
After figuring out how to start it automatically when the machine gets restarted (which happens once in a while when some kernel software upgrade requires it) the server did its job.
Quite another question, however, is how it does its job.
And there the problem lies.
The web-server coming with Calibre serves pages that are heavily dependent on JavaScript; so much so that the pages simply don't appear or work at all if you have JavaScript disabled in your browser e.g. for privacy or security reasons.
For a while I grudgingly activated JavaScript whenever I wanted to access my books remotely.
I asked the author of Calibre whether he'd be willing to provide a barrier-free alternative (i.e. without JavaScript) but unfortunately he declined: "Not going to happen."
Well, due to other projects I didn't find the time then to do something about it, and it took some more years before I started seriously to look for alternatives.
Therefore now there's Kaliber, a barrier-free web-server for your Calibre book collection.
It doesn't depend on – or even need – JavaScript, but just requires a web-browser capable to read plain HTML on the remote user's side.
So even privacy or security conscious people or those who depend on assisting technologies (like e.g. screen-readers) can now access their library.
As an aside:
I never really understood the desire to multiply the work needed to be done for a web page.
A server is a server which means it should serve. When in a restaurant ordering a meal you surely expect it to be brought to you fully prepared and ready to be consumed. You'd probably were seriously annoyed if the waiter/server just brought you the ingredients and left it to you to prepare the meal for yourself.
For some strange reason, however, that's exactly what happens on a growing number of web-presentations: Instead of delivering a ready-to-read web-page they send every user just program code and let the user's machine do the preparing of the page. In other words: Instead of one server doing the work and delivering it to thousands of remote users nowadays the server forces thousands (or even millions) of remote users to spend time and electricity to just see a single web-page.
Since I couldn't find a documentation of the database structure and/or API used by Calibre to store its meta-data I had to reverse engineer ways to access the stored book data.
The same is true – to a certain lesser degree – for the web-pages served by Kaliber: it's kind of a mix of Calibre's normal (i.e. JavaScript based) and mobile pages.
The overall layout of the web-pages served by Kaliber is intentionally kept simple (KISS).
- Simplicity of use;
- Barrier-free (no JavaScript required);
- Books list layout either
Cover GridorData List; - Easy navigation (
First,Prev,Next,Lastbutton/links); - Fulltext search as well as datafield-based searches;
- Ordered in either
ascendingordescendingdirection; - Selectable number of books per page;
- Sortable by
acquisition,author,language,published,publisher,rating,series,size,tags, ortitle; - Anonymised access logging (privacy by default);
- Optional user/password based access control.
You can use Go to install this package for you:
go get -u github.com/mwat56/kaliber
After downloading this package you go to its directory and compile, e.g.
cd $GOPATH/src/github.com/mwat56/kaliber
go build app/kaliber.go
which should produce an executable binary.
$ ./kaliber -h
Usage: ./kaliber [OPTIONS]
-accessLog string
<filename> Name of the access logfile to write to
(default "/home/matthias/kaliber/access.log")
-authAll
<boolean> whether to require authentication for all pages
-booksPerPage int
<number> the default number of books shown per page (default 24)
-certKey string
<fileName> the name of the TLS certificate key
-certPem string
<fileName> the name of the TLS certificate PEM
-dataDir string
<dirName> the directory with CSS, FONTS, IMG, SESSIONS, and VIEWS sub-directories
(default "/home/matthias/kaliber")
-delWhitespace
(optional) Delete superfluous whitespace in generated pages (default true)
-errorlog string
<filename> Name of the error logfile to write to
(default "/home/matthias/kaliber/error.log")
-gzip
<boolean> use gzip compression for server responses (default true)
-ini string
<fileName> the path/filename of the INI file to use
(default "/home/matthias/.kaliber.ini")
-lang string
the default language to use (default "en")
-libraryName string
Name of this Library (shown on every page)
(default "MeiBucks")
-libraryPath string
<pathname> Path name of/to the Calibre library
(default "/var/opt/Calibre")
-listen string
the host's IP to listen at (default "0")
-logStack
<boolean> Log a stack trace for recovered runtime errors (default true)
-port int
<portNumber> The IP port to listen to (default 8383)
-realm string
<hostName> Name of host/domain to secure by BasicAuth
(default "eBooks Host")
-sessionTTL int
<seconds> Number of seconds an unused session keeps valid (default 1200)
-sidName string
<name> The name of the session ID to use
(default "sid")
-sqlTrace string
<filename> Name of the SQL logfile to write to
-theme string
<name> The display theme to use ('light' or 'dark')
(default "dark")
-ua string
<userName> User add: add a username to the password file
-uc string
<userName> User check: check a username in the password file
-ud string
<userName> User delete: remove a username from the password file
-uf string
<fileName> Passwords file storing user/passwords for BasicAuth
(default "/home/matthias/kaliber/pwaccess.db")
-ul
<boolean> User list: show all users in the password file
-uu string
<userName> User update: update a username in the password file
Most options can be set in an INI file to keep the command-line short ;-)
$ _
As you can see there are quite a few options available, but almost all of them are optional since they come with reasonable default values most of which can be set in the accompanying INI-file (in fact, the "default" values shown above are coming from the INI-file used).
Please note that the default values shown above vary depending on the system where
kaliberis called and especially on the contents of the INI file (it's read before the help text is produced).
You don't have to give all those commandline options listed above every time you want to start Kaliber.
There's an INI file which can take all the options (apart from the user handling options) all in one place:
$ cat kaliber.ini
# Default configuration file for the Kaliber server
[Default]
# Name of the optional access logfile to write to.
#
# NOTE: a relative path/name will be appended to `dataDir` (below).
# (Normally this is either empty or the name of the logfile to use.)
accessLog = /dev/stdout
# Authenticate user for all pages and documents.
#
# If `false` only the download links need user authentication
# (see `passFile` below).
authAll = false
# Number of documents to show per page.
booksPerPage = 24
# Path-/filename of the TLS certificate's private key to enable
# TLS/HTTPS (if empty standard HTTP is used).
#
# NOTE: a relative path/name will be appended to `dataDir` (below).
# (Normally this is either empty or the name of the key-file to use.)
certKey = ./certs/server.key
# Path-/filename of the TLS (server) certificate to enable TLS/HTTPS
# (if empty standard HTTP is used).
#
# NOTE: A relative path/name will be appended to `dataDir` (below).
# (Normally this is either empty or the name of the cert-file to use.)
certPem = ./certs/server.pem
# The directory root for the "css", "fonts", "img", "sessions",
# and "views" sub-directories.
#
# NOTE: This should be an _absolute_ path name!
dataDir = ./
# Delete superfluous whitespace in generated pages.
delWhitespace = yes
# Name of the optional error logfile to write to.
#
# NOTE: a relative path/name will be appended to `dataDir` (above).
# (Normally this is either empty or the name of the logfile to use.)
errorLog = /dev/stderr
# Use GZip compression for server responses.
gzip = true
# The default UI language to use ("de" or "en").
lang = de
# Name of this library (shown on every page).
libraryName = "MeiBucks"
# Path of Calibre library.
#
# NOTE: this _must_ be the absolute pathname to your Calibre library.
libraryPath = "/var/opt/Calibre"
# The host's IP number to listen at.
#
# The special value "0" means to listen on all available interfaces.
listen = 127.0.0.1
# Whether or not log a stack trace for recovered runtime errors.
#
# NOTE: This is merely a debugging aid and should normally be `false`.
logStack = true
# The host's IP port to listen to.
port = 8383
# Password file for HTTP Basic Authentication.
#
# NOTE: a relative path/name will be appended to `dataDir` (above).
passFile = ./pwaccess.db
# Name of host/domain to secure by BasicAuth.
realm = "eBooks Host"
# Number of seconds an unused session stays valid.
sessionTTL = 1200
# Name of the session ID field.
sidName = sid
# Optional (debugging) SQL trace file.
#
# NOTE: a relative path/name will be appended to `dataDir` (above).
# (Normally this will be empty and used only for debugging purposes.)
sqlTrace = ./sqlTrace.sql
# Default web/display theme to use ("dark" or "light").
theme = dark
# _EoF_
$ _
An INI-file as shown above is looked for at five different places:
- in your (i.e. the current user's) current directory (
./kaliber.ini), - in the computer's main config directory (
/etc/kaliber.ini"), - in the current user's home directory (e.g.
$HOME/.kaliber.ini), - in the current user's configuration directory (e.g.
$HOME/.config/kaliber.ini), - in the
-ini <filename>commandline option (if given).
All these files (if they exist) are read in the given order at startup before finally parsing the commandline options shown earlier. So each step overwrites the previous one, the commandline options having the highest priority.
Why, you may ask, would you need an username/password file anyway? Well, there may be several reasons one of which could be Copyright problems.
If not all your books are in the public domain and Copyright-free in most countries you may not make them publicly available. In that case you're most likely the only actual user allowed to access the books in your library. Depending on your country's legislation you may or may not include your family members. If in doubt please consult a Copyright expert.
The authAll commandline option (and INI setting) allows you to specify whether access to all pages requires user authentication; if that flag is false then only the download links require authentication, if true any access requires a given username/password pair.
Whenever there's no password file given (either in the INI file passfile or the command-line -uf) all functionality requiring authentication will be disabled which in turn means that everybody can freely access your library.
This is probably not what you want.
Note that the password file generated and used by this application resembles the
htpasswdused by the Apache web-server, but both files are not interchangeable because the actual encryption algorithms used by both are different.
Only usable from the commandline are the -uXX options, most of which need an username and the name of the password file to use.
Note that whenever you're prompted to input a password this will not be echoed to the console.
$ ./kaliber -ua testuser1 -uf pwaccess.db
password:
repeat pw:
added 'testuser1' to list
$ _
Since we have the passfile setting already in our INI file (see above) we can omit the -uf option for the next options.
With -uc you can check a user's password:
$ ./kaliber -uc testuser1
password:
'testuser1' password check successful
$ _
This -uc you'll probably never actually use – it was just easy to implement.
If you want to remove a user then -ud will do the trick:
$ ./kaliber -ud testuser1
removed 'testuser1' from list
$ _
When you want to know which users are stored in your password file then -ul is your friend:
$ ./kaliber -ul
matthias
$ _
Since we deleted the testuser1 before only one entry remains.
That only leaves -uu to update (change) a user's password.
$ ./kaliber -ua testuser2
password:
repeat pw:
added 'testuser2' to list
$ ./kaliber -uu testuser2
password:
repeat pw:
updated user 'testuser2' in list
$ ./kaliber -ul
matthias
testuser2
$ _
First we added (-ua) a new user, then we updated the password (-uu), and finally we asked for the list of users (-ul).
Under the directory given with the datadir entry in the INI file (or the -datadir commandline option) there are several sub-directories expected:
css: containing the CSS files used,fonts: containing the fonts used,img: containing the images used,sessions: containing the remote users' session data,views: the Go templates used to generate the pages.
All of this directories and files are part of the Kaliber package.
You can use them as is or customise them as you see fit to suit your needs.
However, please note: I will not support any customisations, you're on your own with that – and you should know what you're doing.
There are some Calibre features which are not available (yet) with Kaliber and not currently supported:
- custom columns defined by the respective
Calibreuser; - different/multiple libraries for the user to switch between;
- OPDS formatted access;
- book uploads are not planned to be included;
- monitoring your read progress is unlikely to be implemented here (I feel that that's the book reader's responsibility, not the server's).
Once I figure out how they are realised by Calibre I expect some may find their way into Kaliber as well (provided I find actually time to do it).
Like almost every other web-server Kaliber writes all access data to a logfile (logfile = in the INI file and -log at the commandline).
As privacy becomes a serious concern for a growing number of people (including law makers) – the IP address is definitely to be considered as personal data – the logging facility anonymises the requesting users by setting the host-part of the respective remote address to zero (0).
This option takes care of e.g. European servers who may not without explicit consent of the users store personal data; this includes IP addresses in logfiles and elsewhere (eg. statistical data gathered from logfiles).
Since the generated logfile resembles that of the popular Apache server you can use all tools written for Apache logfiles to analyse the access data.
The following external libraries were used building Kaliber:
- ApacheLogger
- Crypto
- CSSfs
- ErrorHandler
- GzipHandler
- INI
- Jffs
- PassList
- Resize
- Sessions
- SQLite3
- WhiteSpace
Copyright © 2019, 2023 M.Watermann, 10247 Berlin, Germany
All rights reserved
EMail : <[email protected]>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
You should have received a copy of the GNU General Public License along with this program. If not, see the GNU General Public License for details.