If you are creating a new application, you can use -O to skip ActiveRecord: rails new my_app -O For existing applications: 1. Remove database adapter gems from your Gemfile (mysql2, sqlite3, etc.) 2. Change your config/application.rb Remove require ‘rails/all line and require frameworks (among those available in your rails version, the list varies, do not … Read more
You should run following command to install NodeJS in Ubuntu sudo apt-get install nodejs or run this for OSX brew install nodejs Uglifier is a JS wrapper and it needs a JS runtime running or JS interpreter. I would choose to install NodeJS.
You can get the integer values for an enum from the class the enum is on: Model.sale_infos # Pluralized version of the enum attribute name That returns a hash like: { “plan_1” => 1, “plan_2” => 2 … } You can then use the sale_info value from an instance of the Model class to access … Read more
In rails 4 you need to make the changes below: config.assets.compile = true config.assets.precompile = [‘*.js’, ‘*.css’, ‘*.css.erb’] This works with me. use following command to pre-compile assets RAILS_ENV=production bundle exec rake assets:precompile Best of luck!
Seems there is a change in handling of attribute protection and now you must whitelist params in the controller (instead of attr_accessible in the model) because the former optional gem strong_parameters became part of the Rails Core. This should look something like this: class PeopleController < ActionController::Base def create Person.create(person_params) end private def person_params params.require(:person).permit(:name, … Read more
run postgres -D /usr/local/var/postgres and you should see something like: FATAL: lock file “postmaster.pid” already exists HINT: Is another postmaster (PID 379) running in data directory “/usr/local/var/postgres”? Then run kill -9 PID in HINT And you should be good to go.
I had almost precisely the same error, and was able to completely fix it simply by running: gem install bundler It’s possible your bundler installation is corrupt or missing – that’s what happened in my case. Note that if the above fails you can try: sudo gem install bundler …but generally you can do it … Read more
I think it should be: scope :find_lazy, -> (id) { where(id: id) }
Just do: gem ‘mysql2’, ‘~> 0.3.18’ this gem works with rails version 4.x.x if install gem ‘mysql2’, ‘~> 0.4.0’ it produces gem load error and causes compatibility issues
Take a look at Concerns Create a folder in your models directory called concerns. Add a module there: module MyConcernModule extend ActiveSupport::Concern included do after_save :do_something end def do_something … end end Next, include that in the models you wish to run the after_save in: class MyModel < ActiveRecord::Base include MyConcernModule end Depending on what … Read more