@girish yet another reason for having the LDAP plugin for Discourse pre-installed and pre-configured on Cloudron would be so that we can start to try and reverse engineer the new Discourse Teams as much as possible (sadly it's not all open source, although as I understand it lots of the features are just using open source plugins)

More info about the difference between Discourse and Discourse Teams:

https://support.teams.discourse.com/docs?topic=85
https://meta.discourse.org/t/comparing-discourse-for-teams-with-discourse/168423/7

Yikes I had made numerous mistakes and it is working now. I had changed my username from admin and I was including the ruby prompts in the commands. I'm still brand new to Cloudron so hopefully I will have less and better questions in the future. Thanks so much @girish

@girish Awesome thanks.

This should be fixed in the latest package.

@ruihildt They renamed a constant from UnicodeUsernameWhitelistValidator to
UnicodeUsernameAllowlistValidator

To fix:

Edit /app/data/site_settings.yml using file manager and replace UnicodeUsernameWhitelistValidator with UnicodeUsernameAllowlistValidator

@girish

Restore completed.

I changed the version to "stable", so there were no downgrade (2.6.0beta7 ->>2.6.0).
rest is simple, (here is steps for anyone who want to migrate)

just install discourse on cloudron, set a demo subdomain to avoid (down time), upload backup file, start restoring process. once restore completed u will logout, signin again with your admin account (The one you use on migrated). go to cloudron dashboard & change to to the real domain. update it from domain register if you use manual domain. be sure in discourse dashboard that the notification email domain is OK. it will take around 1 minute with almost zero down time. to be sure everything is OK, shut down the old server/vps.

I finally tested on a fresh install... and it works. So I dug some more, comparing the two installations, and realized at some point is a JS error on my regular install, linked to the chat integration plugin. In the end the code was outdated (it relied on a deprecated API), so I pulled the last version from git and... it worked.

Long story short: this was a plugin bug 🤷 Sorry for the noise, and thanks for suggesting testing a separate install!

Great - adding the subdomain in Cloudron and setting up Amazon SES login for that fixed the issue so I can now both send (via SES) and receive emails (via a Zoho pop mail box), including reply by email mode.
Thanks for your advice everyone!

@bangden07 Yeah, 1 CPU/2GB is not enough for Discourse+WikiJS+Cloudron+Potsgresql+etc. It's quite a heavy app (it runs ruby/rails).

Hi there,

yes that is possible. The different app instances will run in their own isolated containers on the same VPS

I tried this now in a fresh install and it seems to work.

Please note that you are supposed to run the commands in the app's web terminal (i.e Click the gear button in the cloudron dashboard app -> Console -> Terminal). And then you must put in sudo -E -u cloudron bundle exec script/rails console in the shell. Like below:

5c71c01d-4b8e-449d-9708-c46e356a4a04-image.png