4 ms·

You should def setup a reverse proxy. Our wiki has examples for most of the popular ones: https://wiki.kavitareader.com/en/install/reverse-proxy https://wiki.ka

by majora2007 5y ago

You should def setup a reverse proxy. Our wiki has examples for most of the popular ones: https://wiki.kavitareader.com/en/install/reverse-proxy https://wiki.kavitareader.com/en/install/reverse-proxy

pmontra 5y ago
An offline reading feature would be great. Start the reader, mark some books for offline access, download them, go offline, read them, sync the page number with the server when back online.
- majora2007 5y ago
  Haha I tried this last week with PWAs, but they weren't able to provide the level of control I needed to achieve literally this idea. So it looks like native-ish code is in my future for iOS and Android :( But you can download files and use native readers already.
  - pmontra 5y ago
    Yes, and it's what I do. I copy ebooks from my computer to my phone with Syncthing, read on my phone and... only on my phone :-) I know that there are page syncing services, maybe even a self hostable one from Mozilla but I'm lazy about this. After all my phone is always close to me and the screen is even wider than newspaper columns used to be. Too bad browsers are too crippled to build PWAs with the power of native apps. Thanks for the effort anyway :-)
justinlloyd 5y ago
Setting up a reverse proxy is a good way to access the server or container but I would recommend that nobody do this. I did a quick look through of the code on github and I would strongly advocate against exposing this server to the internet at this time even if it were situated behind a reverse proxy with an encrypted connection. The code is immature and not particularly well hardended, many error messages just spew out to Console and catch clauses are empty/non-logging and don't handle the error. There were several places in the repository pattern that gave me pause, and whilst there was only a limited number of ExecuteCommand invocations wrapped in a helper function, that is not to say there isn't a way to ExecuteCommand or perform other attacks. A malformed PDF, CBR or epub could easily fuzz this server. A VPN connecting to the server, or at the very least, symmetric challenge/response HTTPS with a client key requirement on the reverse proxy, with the server running in an isolated Docker container is the only way I'd expose this service. P.S. I know you are the author of the code and not trying to state anything about the code, but merely that I would be careful exposing it to the internet at this time.

You should def setup a reverse proxy. Our wiki has examples for most of the popular ones: https://wiki.kavitareader.com/en/install/reverse-proxy https://wiki.kavitareader.com/en/install/reverse-proxy

pmontra 5y ago

An offline reading feature would be great. Start the reader, mark some books for offline access, download them, go offline, read them, sync the page number with the server when back online.

majora2007 5y ago
Haha I tried this last week with PWAs, but they weren't able to provide the level of control I needed to achieve literally this idea. So it looks like native-ish code is in my future for iOS and Android :( But you can download files and use native readers already.
- pmontra 5y ago
  Yes, and it's what I do. I copy ebooks from my computer to my phone with Syncthing, read on my phone and... only on my phone :-) I know that there are page syncing services, maybe even a self hostable one from Mozilla but I'm lazy about this. After all my phone is always close to me and the screen is even wider than newspaper columns used to be. Too bad browsers are too crippled to build PWAs with the power of native apps. Thanks for the effort anyway :-)

justinlloyd 5y ago

Setting up a reverse proxy is a good way to access the server or container but I would recommend that nobody do this. I did a quick look through of the code on github and I would strongly advocate against exposing this server to the internet at this time even if it were situated behind a reverse proxy with an encrypted connection. The code is immature and not particularly well hardended, many error messages just spew out to Console and catch clauses are empty/non-logging and don't handle the error. There were several places in the repository pattern that gave me pause, and whilst there was only a limited number of ExecuteCommand invocations wrapped in a helper function, that is not to say there isn't a way to ExecuteCommand or perform other attacks. A malformed PDF, CBR or epub could easily fuzz this server. A VPN connecting to the server, or at the very least, symmetric challenge/response HTTPS with a client key requirement on the reverse proxy, with the server running in an isolated Docker container is the only way I'd expose this service. P.S. I know you are the author of the code and not trying to state anything about the code, but merely that I would be careful exposing it to the internet at this time.