I can attest that it is definitely NOT a good idea to add more Docker images to a CR box outside of CR. CR assumes it has full use of the box, so, anything additional you add can and possibly will break things 🙂
@christiaan I just use Radicale. It’s a more pure implementation, or at least without all the fluff and other restrictions. SOGo has an odd restriction where each reminder list must a calendar list too. So in other words your reminder and calendar apps are going to show the exact same lists, which doesn’t align with my workflow, so I always saw it as working against me in some way.
@girish Will do. It's actually not the first time I've run into the problem and a re-fresh of the API credentials solved the problem, although this is the first time I specifically observed that it was a 500 error vs. a 401.
@nebulon Oh! That's awesome, thank you for being patient and clarifying that for me. I appreciate it. So I see that now, it looks like if I'm reading it right it will only run that part to deploy the plugins if that directory does not already exist, and since it will exist of course then it would never be executed. Makes sense. Thanks again! This definitely helps, I appreciate the education on it too. 🙂
And no, my mail relay does not accept IP whitelisting. It's not a proper mail relay service to be exact, but just a regular mail service with outgoing smtp for authenticated users.
Ah yes, someone was trying to do this with a gmail account as well sometime back (and more recently with a mailbox.org account). I think we have to implement this feature in Cloudron to make this use case work.
Learn docker. This is the base deployment tool for Cloudron. No need to learn compose/swarm etc.
Take some time to learn Heroku. Also see 12 factor app. A lot of ideas for Cloudron app deployment are inspired from these two PaaS concepts. Heroku can deploy lots of different frameworks/stacks, so just pick one you are comfortable with.
And then the tutorial link above should be easy to follow. Without knowing 1 & 2, the tutorial can be hard to understand.
@necrevistonnezr There is no fail2ban on Cloudron. Currently, we just rate limit all authentication routes to minimize risk (and with 2FA and app passwords risks are even lower now). We had a plan to implement firewalling this release (rate limits per IP, block specific IP etc), but already changes were piling up. So, we will have some more advanced firewalling features in a future release.
@girish this all sounds great - looking forward to the next release! 🙂
It would also be really nice if there was a simple way to limit the visibility of apps by domain (perhaps using groups?).
I realise that at present it's possible to create groups and then limit access to specific apps to specific groups, and that could be used now to achieve this, but I'd like a quicker and easier way to say to Cloudron: "this group has access to all apps on this domain" (but none of the other domains) than having to do it app by app.
@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!