[image] Introducing pre-compiled JS assets for self-hosters megaphoneAnnouncements It’s enabled by default. You only need to specify the config if you want to opt-out. Yeah exactly. Any kind of diff in the git repo will cause it to bail out. Re. the sidekiq thing, if you open a topic about it, I’m sure we can work out a way to do it either from a plugin, or maybe we could introduce a new GlobalSetting for it. As discussed, I’m trying to take advantage of this but have hit a snag, because I’m customising: /config/initializers/100-sidekiq.rb Here’s my altered code, I’m: Giving each job an accessible retry count attribute which I’m using in a plugin to change workflow logic depending on the amount of times a job has been retried In the file I’m amending it to Create a custom Middleware class to retrieve the value Adding the class to the chain so it is included require "sidekiq/pausable" require "sidekiq/discourse_event" require "sidekiq_logster_reporter" require "sidekiq_long_running_job_logger" require "mini_scheduler_long_running_job_logger" module Sidekiq::Middleware::Server #<-- NEW class SetRetryCountMiddleware def call(worker, job, queue) worker.retry_count = job["retry_count"] if worker.respond_to?(:retry_count=) yield end end end Sidekiq.configure_client { |config| config.redis = Discourse.sidekiq_redis_config } Sidekiq.configure_server do |config| config.redis = Discourse.sidekiq_redis_config config[:skip_default_job_logging] = false config.server_middleware do |chain| chain.add Sidekiq::Pausable chain.add Sidekiq::Middleware::Server::SetRetryCountMiddleware #<-- NEW chain.add Sidekiq::DiscourseEvent end Presently I’m achieving that with a file edit script in app.yml using sed This breaks the hygeine of the repo, so I can’t use the bundled compiled assets. Any suggestions on how to make these modifications from a plugin?

Does the specific position in the stack matter? I tried this in a plugin.rb and it seemed to add the middleware :crossed_fingers: class BreakEverythingMiddleware def call(worker, job, queue) puts "The middleware worked!" raise "THE MIDDLEWARE WORKED" end end Sidekiq.default_configuration.server_middleware { |chain| chain.add BreakEverythingMiddleware }

Making edits to the sidekiq initialising config

Development

merefield (Robert) August 5, 2025, 3:26pm 3

Shouldn’t do!

Great suggestion, I’m going to try that out! Thanks!

Topic		Replies	Views
Sidekiq is being paused, how can I discover why? Product Support	17	3498	September 19, 2018
Sidekiq failing to render after rack gem upgrade Bug	1	1341	January 13, 2020
Sidekiq stops after some time Self-hosting	7	1363	June 14, 2023
Sidekiq not working Self-hosting	9	1374	September 2, 2023
Sidekiq fails to start after Zeitwerk on docker dev Development	24	3841	January 12, 2020

Making edits to the sidekiq initialising config

Related topics