In the “General plugin questions” discussion, Ed_Bobkov asked three questions regarding Discourse plugins.
First, they inquired about the possibility of a site breaking due to a plugin update or core Discourse code change after installing a plugin and rebuilding the app. Falco clarified that the site should remain working until Discourse or plugins are updated, or a browser update breaks Discourse.
Second, Ed_Bobkov asked about the best practice for installing plugins, whether from official GitHub accounts or by copying them to a personal account. Falco advised against forking plugin repositories, as it brings the burden of keeping up with changes upstream.
Third, Ed_Bobkov asked how to view all tables in the database. Falco provided the command ./launcher enter app, followed by su postgres and psql.
Later, Ed_Bobkov asked about resetting a specific plugin’s settings in the database. Falco explained that there is no catch-all reset to default, as every plugin is different. Ed_Bobkov further explained that they want to disable an option that caused problems with the plugin and are looking for a way to change this setting in the database.
I have a general question concerning my understanding of Discourse work with plugins.
Question1. I installed some plugin, rebuild an app. If I don’t change anything, is there a possibility that site will be broken because of the plugin update or a core Dicsourse code change?
A I understand, the command ‘rebuild’ makes a snapshot of core files and plugin and puts these compiled filed in a docker. And no change can change this docker image. Am I right?
Question 2. What is the best practice - to install plugins from the official github accounts or to copy them to your own account and then install it from your place?
Question 3. How can I see all tables in the database?
For example, I need to change settings of a plugin in the db. How can I do it?
If after the install everything is working it should stay working until:
You update Discourse or/and plugins
A browser updates and breaks Discourse
If you fork plugin repositories you bring the burden of keeping up with changes upstream. That includes checking for new security issues that were fixed in the main repo and merging and deploying those.
Hm, I’ll explain, the plugin started causing a problem after a activated one option within it.
Without this option it was working. I would like to set off this option. But when I install the plugin the site becomes unavailable. So I thought that it is possibl to change this setting in the database. How is it possible to do?