While deploying to Heroku, I get a set of deprecation warnings about the vendor/plugins folder (see below). Mine has a .gitkeep statement in it, and nothing else. Is there anything I need to do?
2012-12-13T02:56:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/config/environment.rb:5)
2012-12-13T02:56:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/config/environment.rb:5)
2012-12-13T02:56:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/config/environment.rb:5)
Heroku has already pointed this out and they are already working on it for Rails 4
Heroku works by injecting plugins and it causes this to happen
-----> Rails plugin injection
Injecting rails_log_stdout
Injecting rails3_serve_static_assets
Rails 2.3-style plugins and deprecation warnings running task in Heroku
I just noticed a workaround that Heroku has now.
Injecting plugin 'rails_log_stdout'
Injecting plugin 'rails3_serve_static_assets'
Add 'rails_12factor' gem to your Gemfile to skip plugin injection
Related
My plugins are working fine and appear locally, but as I push my app on Heroku, the plugins index page is empty and there is no plugin...
I've removed everything from my .gitignore to be sure, as suggested here and I've also ran heroku run rake redmine:plugins:migrate.
I've got the following depreciation warnings but I don't know if it comes from here:
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/Rakefile:7)
Plugins in vendor/plugins (/app/vendor/plugins) are no longer allowed. Please, put your Redmine plugins in the `plugins` directory at the root of your Redmine directory (/app/plugins).
However, my plugins are already included in the 'plugins' directory and I'm now kind of stuck on how to solve this problem...
Rails v3.2.17 with Redmine v2.5.1.
Thanks!
In the meantime, I found that it might be related to git submodules problem, as the redmine_app_timesheets folder was present but figured to be empty while running 'heroku run bash'.
So I deleted the two folders and reinstalled the plugin using:
git submodule add https://github.com/maxrossello/redmine_app__space.git plugins/redmine_app__space
git submodule add https://github.com/maxrossello/redmine_app_timesheets.git plugins/redmine_app_timesheets
Plugins are now working, just not sure what configuration I might have lost deleting the local plugins.
I am getting the following deprecation warning:
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released.
My two plugins are render_component and verification. How should I go about bundling these as gems, or should I place them in another file?
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Rails 2.3-style plugins and deprecation warnings running task in Heroku
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support
for these plugins will be removed in Rails 4.0. Move them out and bundle them i
n your Gemfile, or fold them in to your app as lib/myplugin/* and config/initial
izers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonr
ails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required
)> at /app/Rakefile:7)
shows 3 times, sometimes shows 2 times what it means? is there any special meaning?
How to solve this problem for db:migrate
Heroku "injects" some plugins during slug compilation.
-----> Rails plugin injection
Injecting rails_log_stdout
Injecting rails3_serve_static_assets
See Rails 2.3-style plugins and deprecation warnings running task in Heroku
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
eliminating Rails 2.3-style plugins and deprecation warnings
I get the following error when I do a heroku run console:
$ heroku run console
Running `console` attached to terminal... up, run.1
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out an d bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/config/environment.rb:5)
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out an d bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/config/environment.rb:5)
Connecting to database specified by DATABASE_URL
Loading production environment (Rails 3.2.8)
irb(main):001:0>
However, the only file I have in vendor/plugins is .gitkeep:
$ ls -lha vendor/plugins/
total 0
drwxr-xr-x 1 Scott Administ 0 Sep 7 12:26 .
drwxr-xr-x 1 Scott Administ 0 Sep 7 12:26 ..
-rw-r--r-- 1 Scott Administ 0 Sep 7 12:26 .gitkeep
I even tried removing the .gitkeep file and I still get the same deprecation warning. Do I have bad plugins? This is a relatively new Rails project.
Heroku injects old-style plugins to make your app work on their server (specifically to redirect logs to stdout, and to serve static assets from rails). Check the output from a git push... you'll see something like this
-----> Rails plugin injection
Injecting rails_log_stdout
Injecting rails3_serve_static_assets
So it's not something you've done, and nor is it anything to worry about! These will work just fine on Rails 3.x and Heroku will no doubt work something out when Rails 4 is a bit more mature.
I'm getting this deprecation error on my rails 3.2 project which I upgraded from a rails 3.1 project:
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/01/04/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/Rakefile:7)
I'm trying to get rid of this error, but I can't seem to find the plugin. I have already deleted the plugin from vendor/plugins.
If your vendor/plugins is completely empty, then I bet you're deploying to Heroku. As part of the deploy process, Heroku injects plugins into your application. Check out this Stackoverflow answer for an actual Heroku response to this issue.