Bundling more popular plugins with Discourse core

[david (David Taylor)]

Over the next couple weeks, we’ll be moving a number of popular Discourse plugins into the core repository. That means that Discourse will come with a larger number of plugins by default, and it’ll be easier for us to keep them all tested & up-to-date.

All these plugins will remain disabled by default, so this won’t have any visible impact on existing communities.

Self-hosted communities

If you self-host Discourse, and are already using one of these plugins, you’ll be prompted to remove the relevant line from your app.yml file before your next rebuild.

HINT: The plugin 'discourse-reactions' is now bundled with Discourse and should not be included in your container configuration.
Remove the line 'git clone https://github.com/discourse/discourse-reactions' from your containers/app.yml file, then try again.
For more information, see https://meta.discourse.org/t/373574

Development Environment

If you already have one of the plugins installed locally, and then pull the latest version of Discourse core, one of two things will happen.

1. If you use symlinks for your plugins, then you’ll get an error during git pull. To resolve the issue, delete the symlink, then run git pull again

2. If you clone plugins directly, then the git pull of core will succeed, but you will have some surprising ‘unstaged changes’ caused by the nested git repositories. The best way to proceed is to delete the affected directory, and then restore it from main. For example:

   rm -rf plugins/discourse-reactions
   git restore plugins/discourse-reactions
   

Affected Plugins

• discourse-reactions

• … more coming soon

[Richie (Richie Rich)]

Thanks for providing the full HINT line in the first post here, this helped me diagnose a failed rebuild this morning