Best posts made by d19dotca

Just curious how others organize their Cloudron "My Apps" dashboard. Do you use the labels feature much or just descriptive app URLs to keep them organized? Do you bother with tags? And if you use tags, what are some examples you do to solve problems?

I currently have about 20 apps deployed across roughly 12 domains, and am not having too much difficulty yet with organization but I can imagine a year or two down the road (if I'm still using Cloudron which I assume I will be for now) I may run into issues keeping everything straight in the Dashboard, so figured I'd see what problems people have run into and what they've done to solve them when it comes to organizing their apps.

I was going to write a blog post on this one day but here is a quick summary of what I found in moving roughly 12 WordPress sites to the WordPress app in Cloudron...

1. Use the All-In-One WP Migration plugin (https://wordpress.org/plugins/all-in-one-wp-migration/) to export the site, being sure to check the boxes in advanced section that say "Do not export must-use plugins" (if you don't do this it will overwrite the must-used plugins for LDAP authentication in the Cloudron implementation of WordPress)

2. Setup a new base WordPress site in Cloudron, and add in the same All-In-One WP Migration plugin. Now import the site file that was created in step one above.

3. After it's done importing, restart the WordPress site in Cloudron so that it can re-connect it's must-use plugins (initially I find access is lost to the main LDAP admin user until a restart).

4. Once in using your LDAP admin user, remove any old admin user and replace with the new one if you wish, and clean-up any unnecessary plugins and themes that are there by default.

Not only did I find this to be the quickest method but also the safest in terms of not losing anything at all. When I tried the Cloudron blog method it just seemed like a lot of extra work for me. But maybe that's because most of the sites I've designed aren't simple blogs, so maybe their method is still better for simple blog sites.

Enjoy.

When deleting a mailbox, I get the following message: "After deletion, emails to this mailbox will bounce. Note that the mailbox data is not removed."

How do I completely get rid of all history of that account and it's corresponding data? What I had was email1@example.com while testing and now have settled on email2@example.com, and want to remove email1@example.com from the server while ensuring the catch-all is set to email2@example.com so that emails addressed to the email1@example.com still carry over to email2@example.com. However the way the message is worded, it almost seems like email to email1@example.com will bounce instead of progressing in the form of catch-all to email2@example.com.

Can you please clarify how this works exactly, and if anything further needs to be done to remove the mailbox data itself from email1?

Sorry if this is a newbie question (somewhat new to Cloudron) but how does one install this as a community app? I have the option for unstable apps showing enabled, but I do not see Bitwarden in the list of apps I can install. Am I missing something?

I noticed there's a request in the Git for Cloudron to better expose the Spam settings as it's basically a blackbox right now, but in the meantime I was wondering how to change the default of "5" for marking spam in SpamAssassin, if I wanted to make it 4 for example, how would I do that? And would that change stay throughout reboots or be overwritten on reboot? And if it doesn't make sense for making this change yet, is there an ETA for 4.2?

For what it's worth, I have used Rspamd as part of a server I hosted using the Hardware/Mailserver docker containers, and out of the box it was a huge improvement to spam filtering for me. Unfortunately since moving to Cloudron's mail server, I'm getting way more spam going straight to my inbox with no real way of configuring it further either. Would love to see this improved, and Rspamd may be a big piece of the puzzle if my previous experience is anything to go by.

Hello,

I am aware of the documentation for migrating Cloudron to a new server, but am unaware of how to test this while still keeping the old one running temporarily. Maybe I'm missing something or this is a total noob question, but wouldn't I run into licensing issues at that point having effectively two Cloudrons running?

The reason I bring this up... I'm considering moving away from a VPS at one provider and moving to another provider, but since I've never done the migration of Cloudron before I want to ensure I know how to do it first, particularly because there are a dozen client sites hosted on it right now and in particular two client domains that I have no control over their DNS as it is managed by another team for them, so I often have to wait for them to update the IP address before I can finally kill off any old server in favour of the new one.

So what I'm hoping to do is test the process, and once I know it's good, do a final restore point for any new emails that may have arrived in the hours or days between and then cut-over to the new server once and for all. But I have a few concerns such as the automatic DNS stuff... so I have many of my domains on DigitalOcean DNS and Cloudron controls it for me automatically. When I migrate to a new server, will it overwrite all the IP addresses for all of those domains right away, or will it wait for me to do something first? That's the part I'm most worried about in running this test. That and licensing of course.

How could I go about restoring/migrating to a new server while being in compliance with my license for Cloudron and not messing things up for my clients?

Any help would be appreciated.

@d19dotca said in How does the memory management work with regards to "low on resources" message when deploying a new app?:

be improved though to be clarified or with a link to the documentation where a new section would be written about memory management and how it works.

Ah okay, thank you for the clarification. I had just added an edit to my post at the same time as you confirmed it too.

Might I suggest this be improved though to be clarified or with a link to the documentation where a new section would be written about memory management and how it works. I'm in support for my day job so I always go "How can I keep users from needing to contact me", haha, and basically write out as much documentation as needed to prevent calls and stuff. This may make it easier for users going forward too as you have more onboard to Cloudron.