@jdaviescoates said in Plugin folders need ownership change after installation:

I'm very bemused by this.

The first time I installed a plugin (the Akismet plugin) I didn't have to change permissions on the /app/code/plugins/discourse-akismet/ folder from root to cloudron

But every other plugin I've installed after that has required me to open the File Manager and change the ownership from root to cloudron.

Why?

Because the first time, when I installed the Akismet plugin, I restarted the app before looking at the File Manager, and seemingly restarting the app fixes the permissions.

I deleted the chat-integration plugin and reinstalled the checklist plugin and now I am able to see /admin/plugins again.

This happens every time I rebake posts too

sudo -E -u cloudron bundle exec rake posts:rebake

Seems the proposed method is indeed to just delete the directory:

@girish said in How to deinstall plugins:

I think just deleting the plugin directory inside /app/data/plugins and restarting the app will do it.

@staff that info should be added to the docs 🙂

But, also, does removing the directory actually make Cloudron then edit the app.yml file to remove references to the plugin?

Because that is what is supposed to happen as per:

https://meta.discourse.org/t/how-to-completely-uninstall-remove-a-plugin/55034/18?u=jdaviescoates

Working on this in parallel and just wanted to dump the status so far.

The reason discourse does not start is the instructions are "git clone" and that checks out the latest plugin code which is sometimes incompatible with the installed discourse version.

https://meta.discourse.org/t/pinning-plugin-and-theme-versions-for-older-discourse-installs/156971 says "You can now include a .discourse-compatibility file at the root of a plugin or theme repository, that designates what to checkout when installing on older Discourse versions."

Very nice, so we have to figure how to checkout the correct version. And Indeed that calendar plugin has moved on to min compat version of 2.9beta of discourse, we are only on 2.8 still.

https://meta.discourse.org/t/migration-failed-on-update-calendar-plugin-to-last-commit/239437 and https://meta.discourse.org/t/cloudron-missing-plugin-pull-compatible-all/244002 suggests there is some plugin:pull_compatible_all rake task. So, we have to figure how to use this in Cloudron.

@LoudLemur Right, it will be like so:

bundle exec rake plugin:install_gems['discourse-calendar']

This issue has not been solved.

The issue appears to be Cloudron specific and so clearly @Staff need to do something to make Discourse plugins install/ work as expected.

If I can't install the discourse-calendar on my Cloudron Discourse app then the Cloudron Discourse app is completely useless to me 😞

See e.g. https://meta.discourse.org/t/migration-failed-on-update-calendar-plugin-to-last-commit/239437/6

And https://forum.cloudron.io/post/55230

@subven Thank you! I tried again

@BrutalBirdie said in [SOLVED] Discourse cannot be found:

@LoudLemur
6ecf807e-08b3-4939-bbca-abdfad2a55f0-grafik.png

And whats about that Nice to meet you too we have written to each other in other topic before 😄

and thank you also for your efforts as a member of the Cloudron staff

No worries 👍

Oh, sorry about that! It is terrible to forget somebody who has helped. I think it was because I always thought there were just two staff at Cloudron. I am certainly glad there are more.

I think just deleting the plugin directory inside /app/data/plugins and restarting the app will do it.

@briankb-0 NodeBB FTforumW. 👍

This should be fixed in the latest package.

@girish ****ing amazing! Light mode made me blind to it! 🐶

Could you make an already happy man any happier! 😹

f65208a6-a0b2-4b6a-87ce-62c7c39a4794-image.png

♥

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!

@girish Ah in that case I take it back! (Well, some of it .. I still have concerns re software mix, but ... )

I've now got inbound email setup, but it doesn't seem allow catch-alls (even though the setting is set on cloudron) so each category email needs to be set up as an alias.

I also had to enable masquerading in cloudron email settings, which is probably worth mentioning in the setup docs.

@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

@scooke said in Changing root account email in fresh Discourse install:

sudo -E -u root bundle exec script/rails console

Thanks, it solved the issue 👍