@hollosch said in 3.0 coming?:

I can't use this for installing the chat-plugin!

That's true. I wonder why not?

@staff is the Cloudron Discourse app package coded to only expect github repositories in the format https://github.com/org/repository/ or is it Discourse itself expecting that format? or is there some other problem?

(aside: I guess these posts about installing the chat plugin should be moved to their own thread given it's nothing to do with Discourse 3.0)

My guess: Discourse itself is expecting https://github.com/org/repository/ but in Discourse 3.0 this isn't a plugin that needs installing and is just part of Discourse itself, and so until we get Discourse 3.0 on Cloudron (which we can't have until Cloudron 7.4 because it needs Redis 6.2 or above) we can't use this plugin 😞

Although I guess you could try using the old repo https://github.com/discourse/discourse-chat 🤷 that might still work, but I wouldn't bet on it (although it was only just archived this month and was most recently updated in Nov last year, so could possibly maybe still work?)

(so maybe these posts about the Discourse Chat plugin don't need to move to their own thread because it kinda is directly related to 3.0)

@girish thanks, I guess.

But really it was the the " long standing plugin installation issue" I was actually wondering about not 2.8.14 (despite that being the topic of this thread).

Although now of course I'm also very interested in getting my hand on 3.0! 😄

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.

@nebulon thanks! I'm not getting my hopes up too far, but hopefully this will somehow also resolve all the issues that loads of the official plugins have when trying to install them on Cloudron...

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

This happens every time I rebake posts too

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

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

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

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

Thanks @girish ! It worked. The changes took effect when I ran the job manually.

@LoudLemur Right, it will be like so:

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

New update was 1.17.3-1 and worked perfectly. Thx !

How should I read the doc made by the Cloudron team. 😉

@subven Thank you! I tried again

@robi said in Discourse: initial change email / passphrase problem:

@LoudLemur use a different browser, Firefox may have this issue with certain plugins.

thanks. using a chromium based browser did indeed solve this issue. there is something similar to this if you try and view windy.com in a mozilla browser, the animated wind arrows just disappear and it is streaks of lines across the map.

the whole interent seems to be degenerating into a 'only usable in google products' hell-hole.

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

@brianb said in Installing More Than One Plugin at a Time:

@jdaviescoates handy? NOPE!

I get it... they need to make $ to keep discourse development (or nodebb) funded and moving forward. But after I got Discourse installed I thought there would be a nice UI for the Plugins... nope.

It's not hard but it is tedious.

Best I've been able to do so far is to go to official Discourse github repo and do a search for "discourse-plugin" which is how they tag MOST plugins.

https://github.com/orgs/discourse/repositories?q=discourse-plugin&type=all&language=&sort=

5c0672d4-090d-4836-82a2-864ca508aa82-image.png

I also keep their plugins page pulled up to know what is available and how they prioritize them.

https://www.discourse.org/plugins#business

@brianb Do you think this should be added to the doc for users to find good plugin sources faster?
And if the answer is yes... would you like to contribute that to the doc? 😉

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

@luckow said in How to configure LDAP in Discourse?:

My 2 cents for the moment: please add the LDAP addon to this app, because of the plugin and some use cases, where LDAP makes sense.

+1000000

@briankb-0 said in How to Start Discourse with Plugins Disabled?:

@girish I'm sorry, I've already uninstalled and reinstalling the app

no worries, let us know if you hit it again.

@briankb-0 the launcher script only works with Discourse's own packaging stuff i.e if you use https://github.com/discourse/discourse_docker . It does not work in Cloudron, we have our own packaging at git.cloudron.io/cloudron/discourse-app

Generally, you should be able to do everything using rake or bundle exec since Discourse is just a rails app. See https://docs.cloudron.io/apps/discourse for some examples.

@freetommy Are you behind cloudflare by any chance? IIRC, they have a 100MB upload limit.

Ah, it's similar issue. It's not clear from the logs because that file is not in the manifest, I have fixed the package now to show the error.

Processing by CategoriesController#index as HTML Completed 500 Internal Server Error in 22ms (ActiveRecord: 0.0ms | Allocations: 1948) Discourse::Deprecation (Deprecation notice: use_admin_ip_whitelist is deprecated, use the use_admin_ip_allowlist. (removal in Discourse 2.6) At /app/code/lib/site_setting_extension.rb:211:in `public_send`) lib/discourse.rb:860:in `deprecate' app/models/site_setting.rb:241:in `block (2 levels) in <class:SiteSetting>' lib/site_setting_extension.rb:211:in `public_send' lib/site_setting_extension.rb:211:in `block in client_settings_json_uncached' lib/site_setting_extension.rb:210:in `map' lib/site_setting_extension.rb:210:in `client_settings_json_uncached' lib/site_setting_extension.rb:205:in `block in client_settings_json' lib/cache.rb:94:in `fetch' lib/site_setting_extension.rb:204:in `client_settings_json' app/controllers/application_controller.rb:596:in `preload_anonymous_data' app/controllers/application_controller.rb:407:in `preload_json' app/controllers/application_controller.rb:387:in `block in with_resolved_locale' app/controllers/application_controller.rb:387:in `with_resolved_locale' lib/middleware/omniauth_bypass_middleware.rb:71:in `call' lib/content_security_policy/middleware.rb:12:in `call' lib/middleware/anonymous_cache.rb:354:in `call' config/initializers/100-quiet_logger.rb:23:in `call' config/initializers/100-silence_logger.rb:31:in `call' lib/middleware/enforce_hostname.rb:23:in `call' lib/middleware/request_tracker.rb:198:in `call'

@solarsimon mm, usually that should not be required. Did you set the mail from address of the discourse app in the Email view - https://docs.cloudron.io/apps/#mail-from-address ?

App is out now, we have moved the package to use terser instead.

@jagadeesh-s2104 I have fixed the instructions. The u.activate is not needed anymore. BTW, it seems to update the email address already (despite the above error). Just run u.save! .