Hey Discourse Plugin Gurus, Just a quick question about Discourse plugins and Rails initializers. If a Discourse plugin has a directory called “config” and a subdirectory under “config” called “initializers” does the Discourse Rails app read all the plugin initializer files under the “initializers…

[image] fzngagan: After skimming through this Ruby on Rails Guides: Configuring Rails Applications Yeah, I read that Rails guide a lot lately. Basically, I’m “OK” with how Rails 6 config works (still learning, but getting more and more comfortable each day). I am just wondering if we can u…

[image] neounix: I am just wondering if we can use the same structure in a Discourse plugin (for initializers), if Rails will read the initializers in the subdirectories like they do in Rails 6; or do we have to register the plugin initializer directory as a configuration “asset” (for a lack of …

I believe so too. You load any additional Ruby files you need from within plugin.rb. Here’s an example from the Follow plugin: plugin.rb 0290c4282 after_initialize do Notification.types[:following] = 800 Notification.types[:following_p…

[image] fzngagan: Discourse doesn’t read any ruby file other than plugin.rb as far as I know. It does read the js and config files. All the ruby files have to be require d in plugin.rb. That’s kinda my impression reading though a number of Discourse plugins on GitHub. Seems Discourse only re…

[image] neounix: However, I was hoping I was wrong and there might be a “deeper” integration of Discourse plugins and Rails; as I have been getting very spoiled on how great Rails 6 is. I think there should be a way to require initializer code in plugin.rb too. Did you try this in plugin.rb …

[image] fzngagan: I think there should be a way to require initializer code in plugin.rb too. Did you try this in plugin.rb Yes, that is not a problem calling and loading the initializers in plugin.rb. The reason for my question was because I am currently writing a fairly large Rails 6 app …

[image] fzngagan: live reload the ruby files without restarting the server This is what reloadable_patch is for. If you wrap ruby class changes in reloadable_patch, it should live reload!

[image] markvanlan: If you wrap ruby class changes in reloadable_patch , it should live reload! Can I wrap the whole plugin.rb file inside it for dev? More seriously, how far can we go with it? Also, adding new files or changing any yml files needs a server restart right?

You shouldn’t have to do a reloadable_patch for everything. Many of the methods defined in instance.rb to make plugin development easy, use reloadable_patch internally like add_to_serializer. lib/plugin/instance.rb 66402abe9 @admin_route = { label: label, loc…

Discourse Plugins and Rails 6 config/initializers Question

Development

fzngagan (Faizaan Gagan) October 27, 2020, 1:52pm 10

Yeah, I would love those rails perks being ported to discourse plugins. One of my personal favourite would be able to live reload the ruby files without restarting the server.

Topic		Replies	Views
Developing Discourse Plugins - Part 1 - Create a basic plugin Developer Guides plugin-guides , tutorial	32	84613	July 8, 2025
Rails plugin generator Announcements	49	13781	August 20, 2021
Is it possible to use a local plugin directory with a docker install? Development	39	3385	June 16, 2022
Transforming simple ruby files into a ruby gem Development	5	1132	December 14, 2018
Package a Discourse plugin as a gem Developers plugin-guides , how-to	4	716	July 27, 2023

Discourse Plugins and Rails 6 config/initializers Question

Related topics