Cloudron Forum

@girish said in Possible to make this Discourse Events plugin work on Cloudron?:

I think this one is gosu cloudron:cloudron bundle exec rake plugin:install_all_gems !

That seemed to do the job, I think, maybe.

The plugin seems to have installed:

f2a7dd2f-3d7e-4a27-9a8e-32b3881cf1e0-image.png

But when I try to click on Events as shown above (and which links to https://bridport.events/admin/events ) I get this:

c9f35c86-a31e-46a5-92fb-84c08a968e61-image.png

⚠️ Error loading route
Caused by plugin 'discourse-events-e0079339aeef4bbe41336a3766e010483478c7374fcb7d7e0574c835848c6e01'
(this message is only shown to site administrators)

I also note that when running e.g. gosu cloudron:cloudron bundle exec rake posts:rebake I get:

fatal: not a git repository (or any of the parent directories): .git

I got that a few times during the install process too. 🤔

The package with OpenID integration for Cloudron SSO is released. However this currently only works with new app instances.

@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

I guess installing the ActivityPub plugin in the cloudron context will face similar issue than this here @murgero

@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.

Discourse has OIDC by now. NodeBB has no "supported" plugin, this has to be opened upstream.

This should be fixed in the latest package.

Discourse is more popular than NodeBB for sure. I think it's best to just try out various public forums and decide for yourself. NodeBB based forums are probably harder to find than Discourse ones (atleast for tech forums). The Qt Forum is nodebb though (https://forum.qt.io/)

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!

@bmann you can submit PRs here - https://git.cloudron.io/cloudron/docs/

Discourse docs are at https://git.cloudron.io/cloudron/docs/-/blob/master/knowledgebase/docs/apps/discourse.md?ref_type=heads

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