All Blogs
Written by Kiprosh, team of passionate and disciplined craftsmen turning your ideas into reality.
Kiprosh
is now part of
LawLytics
Written by Kiprosh, team of passionate and disciplined craftsmen turning your ideas into reality.
On "Bundle exec rake assets:precompile", we received an error like,"Rake aborted" and No clue about the problem that created this issue.But on the line which this error was thrown had its reference to excon gem which was running smoothly few days ago. Basically the issue was with recent bundle update, which updated the excon gem from 0.9.5 to 0.9.6 in Gemfile.lock which maintains all dependencies. So inclusion of excon gem with version number 0.9.5 fixed the issue.
It is a warning that may appear in your log. Primary reason for this warning is CSRF_meta_tag is missing in your layout. OR Following are some other solutions to get rid of this WARNING. Add CSRF token in ajax request header using xhr. (Highly recommended) Override the method : verified_request (Recommended to override the check for JSON request only). Skip the method call verify_authenticity_token. Change POST to GET (Token verification is done for requests other than GET)
I have drafted this rails initialization process after thorough understanding and debugging rails lib code. I have also referred rails initialisation guide present here - Initialization guide so I tried make it simpler to understand for all of us. Here is a step by step rails initialization process. (specifically for Rails 3.1.1) Perform following steps before you start learning and understanding this process git clone https://github.com/rails/rails.git cd rails git checkout v3.1.1 Initialization Process When you do "rails s" from inside your rails app folder, it will load "script/