This is an update from a previous article about passenger 5.0.28.
These are the steps I used to setup for 5.1.0 they have changed a bit:
Do this in the root directory of your Rails application.
cp $(passenger-config about resourcesdir)/templates/standalone/config.erb config/passenger_config.erb
![Ansible [DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax](/img/uploads/ansible-deprecation-warning-using-bare-variables-deprecated-update-playbooks-environment-value-uses-full-variable-syntax.jpg)
If you recently upgraded Ansible and you are getting an error like:
[DEPRECATION WARNING]: Using bare variables is deprecated. Update your
playbooks so that the environment value uses the full variable syntax
('{{rbenv_plugins}}').
This feature will be removed in a future release.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
This article assumes you have already setup a Rails 5 project and you have installed npm locally.
Add these to your Gemfile
gem "browserify-rails"
gem "react-rails"
![The Difference between build and new in Ruby on Rails & ActiveRecord] (/img/uploads/difference-build-new-ruby-rails-activerecord.jpg)
new and build are the same.
Rails routing helpers can be imported into any class that you define in your project. The easiest way is to use include Rails.application.routes.url_helpers
Here’s an example of PORO that implements logic for showing a sign_in link or register link depending on if the user exists or not.
I see many project get nested routes wrong. Developers do not use Ruby modules to reflect the relationship between the parent and children nesting of controllers. Here is an example of the wrong way (IMHO). Let’s say we have a customer and the customer has_many orders and has_one profile. Some developers will represent it like this.
/customers path in the file app/controllers/customers_controller.rb
class CustomersController < ApplicationController
def index
...
end
end
The simplest way to test validates_attachment_file_name and validates_attachment_content_type configurations of the Rails model that has a
paperclip attachment is to use the allow_value method in the shoulda gem.
The following example uses rspec to demonstrate.
Will_paginate and Kaminari are both popular Ruby Gems for displaying and parsing pagination in a Ruby on Rails application. I won’t wade into the seething cauldron of debate about which is better suited for the task.
To center the will_paginate pagination links, do the follow.
<div class="pagniation-wrapper">
<%= will_paginate @accounts %>
</div>
Issues I have found when doing Ruby on Rails upgrades of Ruby version 1.8.7 to 2.2 or 2.1:
If you are using cloudfront with Heroku, chances are you will encounter some problems if you are using something like font-awesome. I won’t go into the details of how to setup cloudfont, but your heroku passenger should have the following. First, read the Passenger Documentation for Nginx configuration template.
These are the correct steps:
Do this in the root directory of your Rails application.
cp $(passenger-config about resourcesdir)/templates/standalone/config.erb config/passenger_config.erb