Bug #13171: Plugins with /public/assets prevent Rails starting in development environment - Foreman

Actions

Copy link

Bug #13171

closed

Plugins with /public/assets prevent Rails starting in development environment

Added by Dominic Cleal over 8 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Eric Helms

Category:

Plugin integration

Target version:

1.11.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/3103

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

When a plugin is registered that has a /public/assets directory in its root, Rails can't start up in the development environment. This happens because the assets initialiser tries to serve the public/ directory.

/home/dcleal/.rvm/gems/ruby-2.0.0-p353@foreman/gems/actionpack-4.1.5/lib/action_dispatch/middleware/stack.rb:112:in `push': can't modify frozen Array (RuntimeError)
        from /home/dcleal/.rvm/gems/ruby-2.0.0-p353@foreman/gems/actionpack-4.1.5/lib/action_dispatch/middleware/stack.rb:112:in `use'
        from /home/dcleal/code/foreman/foreman/config/initializers/assets.rb:66:in `block (2 levels) in <top (required)>'
        from /home/dcleal/code/foreman/foreman/config/initializers/assets.rb:64:in `each'
        from /home/dcleal/code/foreman/foreman/config/initializers/assets.rb:64:in `block in <top (required)>'
        from /home/dcleal/.rvm/gems/ruby-2.0.0-p353@foreman/gems/railties-4.1.5/lib/rails/railtie.rb:210:in `instance_eval'
        from /home/dcleal/.rvm/gems/ruby-2.0.0-p353@foreman/gems/railties-4.1.5/lib/rails/railtie.rb:210:in `configure'
        from /home/dcleal/.rvm/gems/ruby-2.0.0-p353@foreman/gems/railties-4.1.5/lib/rails/railtie.rb:182:in `configure'
        from /home/dcleal/code/foreman/foreman/config/initializers/assets.rb:2:in `<top (required)>'

This can happen if you've used the plugin:assets:precompile rake task as used in packages.

Related issues 1 (0 open — 1 closed)