Calibre is a popular self-hosted ebook manager. Github page.

Now, Calibre is a desktop application, not a web application. But there is also Calibre-web, which is a web front end for the Calibre backend.

Should Calibre and Calibre-web be hosted through a single Cloudron application, or 2 separate applications?

Either way, I think these 2 applications could be very powerful on Cloudron.

I think I've managed to get a basic version of Firefly III packaged! You can find the Git repo here. The main thing to note is that the LDAP connection doesn't quite work with Cloudron's system yet. @girish @nebulon I'm hoping one of you can help look through this and see if we can get a proper connection going? If we can link up the LDAP system, I'm happy to write some tests for this app so we can publish it to the Cloudron App Store.

There's also a no-ldap branch available which will let users register their own accounts on the app, not trying to use LDAP at all. If we can't get a successful LDAP connection going, then I can write tests for this version instead for the App Store.

https://sr.ht has recently been deployed to general availability. It seems like a Phabricator like tool in that it has many different aspects. git, CI, mailing list management, wiki, etc.

@necrevistonnezr I actually wrote a post about migrating email hosts using the imapsync tool that girish recommended, you can check it out here. Note that my post is a bit more extensive as I also migrated registrars and had other active emails there that weren't mine, so yours should hopefully be a bit easier than the whole tutorial!

@girish I believe I've completed the development of PrivateBin for Cloudron! You can view the source here. It's currently working on the latest 1.3.1 release and has Selenium tests for the app's basic functionality. I'd love for it to be published to the Cloudron App Store - let me know if you need anything else!

@yusf I entirely agree, but in my research so far, all of the stable self-hosted ebook solutions rely on Calibre as a server for some strange reason. I agree that packaging a desktop app for Cloudron is weird, but there is a way to start up only the server-side piece of it, enabling a web solution, like CalibreWeb, to access it.

I'm trying to use the built-in email feature. I am hosting my Cloudron on AWS and filled out the appropriate forms. I have all check marks down the email page and am able to send email from my Cloudron account just fine, but when I try to email my Cloudron account, I get a 'Mail delivery failed' message a few days later. Has anyone had something similar happen?

@fbartels this looks great! I'd like to give it a try, but I'm not sure what the 'first time' message is talking about - what's a TURN server, and if I don't have it configured, is it really entirely self hosted?

@yusf Calibre itself is quite a lot of things as I understand it. The important part here would be the server component. With Calibre installed locally, then Calibre-web would be the web interface to the server.

I've done some research on open source ebook software out there, and Calibre is the one that always comes up with the most community support. Open to other suggestions!

Inlets is an ngrok alternative so you can tunnel your localhost to your self-hosted server.

I know there are a few similar projects like this out there, one of this is localtunnel, but it looks like inlets has been more active recently which is why I listed that one. Happy to hear about other alternatives based on experience!

@girish yep, should've included that in the previous post...
This is the main repo I've been working from. I've been trying to package both the sync-server and web repo's in here, but the server isn't working properly the second I move it from port 3000 (which is declared in the Manifest). I forget in what state this is in at the moment, but I know that commit 8b31274fd32a430616adee81ea9a2ecb15a133b4 and the initial commit have the server up and running properly.
Once I realized the tcpPorts might be the issue, I also created this repo which only packages the web app, this works successfully.
It's not the end of the world if they're not in the same repo, I have it working locally with the 2 repos talking to one another, but it would be quite nice if they could be packaged together

@girish when packaging both repos together, I'm trying to use the tcpPorts for the syncing server, but keep getting this error in the logs when I try to interact with it through the app:
HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
I'm assuming this means that the syncing server does in fact need HTTP traffic coming through, not simply TCP. You mentioned there's only 1 http port that can be exposed per Cloudron app, do you see any way to accomplish this besides splitting the server piece and front end piece into 2 Cloudron apps?

@yusf womp womp I guess all the more reason to try and package Calibre?

@yusf I have a Calibre instance up and running on a VM (so only the server side piece) and I followed this tutorial to get it set up. The main piece to follow there is the Run Calibre Server section. This guide also just reminded me that user management on Calibre is entirely unique and not easy to manage eyeroll

As for other front ends, I am currently using CalibreWeb on that same VM and it works mostly well, but am open to other suggestions.

And as for COPS, that actually looks like it might be a replacement for Calibre entirely?? I'm very open to that!

Hello!

I recently updated the domain provider for a domain of mine that is hosted through Cloudron (trying to completely detach myself from AWS...). When I made the switch (to Namecheap, which is already enabled and whitelisted through another domain I have hosted on Cloudron), it didn't create any DNS records in Namecheap for the current apps I have hosted on the original domain. It only created a record one by one if I went to each app in the dashboard, went to Location and hit 'Save'. I ended up creating the records manually. Unless I did something wrong, this might be something that was overlooked in the transition code?

Just wanted to mention in case this is an actual issue!

Thanks!

Tomer

@yusf I entirely agree, but in my research so far, all of the stable self-hosted ebook solutions rely on Calibre as a server for some strange reason. I agree that packaging a desktop app for Cloudron is weird, but there is a way to start up only the server-side piece of it, enabling a web solution, like CalibreWeb, to access it.

@necrevistonnezr I actually wrote a post about migrating email hosts using the imapsync tool that girish recommended, you can check it out here. Note that my post is a bit more extensive as I also migrated registrars and had other active emails there that weren't mine, so yours should hopefully be a bit easier than the whole tutorial!

First thing in the readme: Note: There might be thousands such solutions available already! :D

Inlets is an ngrok alternative so you can tunnel your localhost to your self-hosted server.

I know there are a few similar projects like this out there, one of this is localtunnel, but it looks like inlets has been more active recently which is why I listed that one. Happy to hear about other alternatives based on experience!

@girish I believe it's a non-http port, yes. I've been through the docs so many times before and can't believe I missed the tcpPorts and udpPorts in the Manifest file looks like that's a solid starting point!