ActionController::Routing Error when adding official plugins

Development

AI-generated summary

A user reports an ActionController::RoutingError when trying to load official Discourse plugins in a development environment on Ubuntu, with errors indicating missing asset routes for various plugins. Another user, merefield, experiences a similar issue and investigates the cause. They determine that the problem stems from a non-standard development setup where Ember CLI runs in a separate container, sharing a volume with the Rails server. The key issue is that the plugins directory wasn’t accessible to the Ember CLI process, which was responsible for building the JavaScript assets. After adding the plugin mappings to both containers, merefield resolves the issue. The discussion highlights the importance of ensuring both the Rails and Ember CLI processes have access to the necessary plugin files in a shared volume setup.

1

Hello!

I’m running 2.9.0.beta11 on Ubuntu (developer environment) and I get the following errors about these plugins. It works perfectly fine without them. What do I need to do to get these plugins working?

ActionController::RoutingError (No route matches [GET] "/assets/plugins/discourse-adplugin.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
ActionController::RoutingError (No route matches [GET] "/assets/plugins/discourse-canned-replies.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
ActionController::RoutingError (No route matches [GET] "/assets/plugins/discourse-cakeday.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
ActionController::RoutingError (No route matches [GET] "/assets/plugins/discourse-checklist.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
ActionController::RoutingError (No route matches [GET] "/assets/plugins/discourse-solved.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
ActionController::RoutingError (No route matches [GET] "/assets/plugins/discourse-spoiler-alert.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
ActionController::RoutingError (No route matches [GET] "/assets/plugins/docker_manager.js")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/missing_avatars.rb:23:in `call'
lib/middleware/turbo_dev.rb:34:in `call'
2

Working on a very similar issue too, in dev.

Did you find a solution?

It looks like for some reason, this code is not firing or files are ending up in the wrong place.

That in turn looks like Ember CLI has not successfully built.

And yet I’ve got Build successful (70398ms) – Serving on http: ...

3

How are you starting your development servers? Are you running bin/ember-cli?

4

Yes. It’s a non-standard dev install though, I’m running ember-cli on a separate container, sharing a volume with the rails server (investigating if this is the problem)

5

My main question is: why are you doing that? :stuck_out_tongue:

Things to check:

  • Does the ember-cli process have access to the plugins directory?

  • What does your shared volume include? The whole Discourse directory? In particular, I’m thinking of public/assets and app/assets/javascripts/discourse/dist

  • Where are your HTTP requests going? Ember-cli’s proxy? Or straight to the Rails app? (either can work, but knowing which way round you’re doing it may help debug)

6

Thats my current config, but checking

They are going to Ember, and it’s proxying to the rails port.

Don’t ask :sweat_smile: (educational stuff though debugging the pipeline!).

Useful avenues to check. Was just curious how the OP got on.

I will report my findings for the benefit of others doing crazy configs.

Update:

Ooops, this is where I think I’ve messed up!!

I forgot to add the additional plugins to both containers…

7

@david that was the issue. I’d added a load of ‘local’ volume plugin mappings and forgot to add all of them to both containers :man_facepalming:

so presumably it had all the nice Ruby on Rails, but none of the Javascript on tap …

It’s now working :beers:

@hyphalos let us know if you are still struggling and we might be able to help …