Update server TODO

This commit is contained in:
Kovid Goyal 2018-07-01 10:19:50 +05:30
parent 70431be166
commit 6fa0be8c16
No known key found for this signature in database
GPG Key ID: 06BC317B515ACE7C

View File

@ -18,7 +18,7 @@ New features for the in-browser viewer
New features for the server generally New features for the server generally
--------------------------------------- ---------------------------------------
- Create a UI for converting, sending by email, etc. - Create a UI for sending by email
- Add a way to search the set of locally available books stored in offline - Add a way to search the set of locally available books stored in offline
storage. storage.
@ -26,15 +26,14 @@ New features for the server generally
- Automatic Let's Encrypt integration so that using HTTPS is easier - Automatic Let's Encrypt integration so that using HTTPS is easier
Should wait for the acme v2 protocol endpoint: Should wait for the acme v2 protocol endpoint:
https://letsencrypt.org/2017/06/14/acme-v2-api.html https://letsencrypt.org/2017/06/14/acme-v2-api.html
Turns out this fairly pointless to do, since it only works if the server
is running on port 80, which is a privileged port.
- Some way to manage remote calibre server instances via the calibre GUI. Two - Some way to manage remote calibre server instances via the calibre GUI. Two
possibilities are: possibilities are:
1) Have the remote server appear as a "device" in the GUI. You can then 1) Have the remote server appear as a "device" in the GUI. You can then
send books to the remote server, update metadata, etc. just as you would send books to the remote server, update metadata, etc. just as you would
when connecting calibre to a real device. when connecting calibre to a real device.
2) Have the remote server appear as a library in the GUI 2) Have the remote server appear as a library in the GUI
(2) is preferable in terms of features/functionality, but is (2) is preferable in terms of features/functionality, but is
**much** harder to implement in a performant and semantically correct manner. **much** harder to implement in a performant and semantically correct manner.
Bug fixes
--------------