In a discussion titled “Advice on Installing Plugins” under the Self-hosting support category, nap, a new Discourse administrator, seeks guidance on installing approximately 10 plugins from the all-the-plugins repository. They express concern about potential compatibility issues, abandoned plugins, and future core update conflicts. ondrej directs them to a helpful meta.discourse.org guide on plugin installation. nap then asks whether plugins can be installed via the Admin Plugin UI or require manual edits to the app.yml file. They further observe that Discourse’s admin interface often requires server-level access (SSH), which may not always be feasible or desirable nap. pfaffman confirms that non-official plugins carry a risk of breaking after upgrades and that SSH access is required for plugin installation—even with discourse_docker, occasional command-line upgrades are still necessary. Stephen clarifies that Discourse is fundamentally a JavaScript application built from app.yml, and plugins are integrated during the build process. He advises that if this architecture is problematic, considering an alternative open-source platform may be prudent. The consensus underscores the necessity of SSH access and the risks associated with third-party plugins, especially regarding long-term maintenance and upgrades.
I’m new to administering a Discourse forum, so pardon this question.
I’m considering installing about 10 plugins listed at https://github.com/discourse/all-the-plugins/tree/master/plugins onto our new Discourse site.
Before I go ahead and install them, I’m wondering if there are any ‘gotchas’ that I should be aware of? I’m thinking of things like compatibility issues, forsaken plugins, etc. Will any of the plugins listed cause potential problems with updates to the core Discourse engine in the future?
Is there a reference I can read that will give me an appreciation for the developer’s policy in this regard?
I’m beginning to see a bit of a trend in the admin aspects of Discourse.
It appears that the forum admin controls many parameters that a server admin role is usually responsible for, and here there is a need for ssh access to the server. Unfortunately, this is not always possible, nor desirable for that matter.
If they aren’t official, then there is some chance that they’ll break when you upgrade.
Yes, you’ll need ssh access to install plugins. Even with discourse_docker, which will let you upgrade without ssh access, you still need to do a command line upgrade a few times a year.
Desirable or not, that’s how Discourse is built and runs.
Discourse isn’t a website, it’s a Javascript application, and that application is built from the app.yml. Plugins are pulled down during that build process.
If you dislike the delineation and it’s going to have an operational impact I would suggest looking for a different open source discussion platform.