Tag: RVM

Puma Jungle script fully working with RVM and Pumactl

Finally I've decided to switch some of my services from Apache+Passenger to Nginx+Puma. Passenger was very convenient when having more than one app per server. Although I used Passenger Standard edition and sometimes apps that should have max 1-2 workers would consume at least half of pool. I was not able to prioritize apps easily. Also it started to get pretty heavy and disadvantages finally exceeded benefits of using it.

Switching static and PHP-based content from Apache to Nginx was really simple. I've installed Nginx, started it on port 82 and 445 for HTTPS and to maintain uptime, I just proxy passed each app at a time from Apache to Nginx. That way I kept Apache temporarily as a proxy engine for all the "simple to move" content and as a Passenger wrapper for my Rails apps.

I've decided to use Puma as my default Rails server for apps on this particular machine. Everything worked great until I've tried to use Jungle script to manage all the apps at once (and add it to init.d). After few seconds of googling I found Johannes Opper post on how to configure Puma Jungle to work with RVM. It turned out, you just need to edit /usr/local/bin/run-puma file and add this line:

# Use bash_profile of your rvm/deploy user
source ~/.bash_profile

After that I was able to start all the apps at once:

/etc/init.d/puma start

Unfortunately, I was not able to stop/restart Puma instances with this script. It was giving me this message:

# when stopping
/etc/init.d/puma: line 99: pumactl command not found
# when restarting
/etc/init.d/puma: line 129: pumactl command not found

Since there's an RVM on the server, Puma was installed as one of gems for one Ruby version. The same goes for Pumactl. To be able to use Pumactl I had to change the /etc/init.d/puma script a bit. First I had to change it from sh to bash script:

#! /bin/bash
# instead of
#! /bin/sh

After that I had to add my deploy user bash profile:

source ~/.bash_profile

and change how pumactl is executed in few places:

do_stop_one method (line 99):

# replace this
pumactl --state $STATEFILE stop
# with this
user=`ls -l $PIDFILE | awk '{print $3}'`
su - $user -c "cd $dir && bundle exec pumactl --state $STATEFILE stop"

do_restart_one (line 129):

# replace this
pumactl --state $dir/tmp/puma/state restart
# with this
user=`ls -l $PIDFILE | awk '{print $3}'`
su - $user -c "cd $dir && bundle exec pumactl --state $dir/tmp/puma/state restart"

do_status_one (line 168):

# replace this
pumactl --state $dir/tmp/puma/state stats
# with this
user=`ls -l $PIDFILE | awk '{print $3}'`
su - $user -c "cd $dir && bundle exec pumactl --state $dir/tmp/puma/state stats"

and that's all. After that you should be able to manage all your Puma apps with Jungle.

Upgrading to Rails 4.0 from Rails 3.2 – Test case – Part II (assets, models)

Here's the second part of tutorial on how to migrate from Rails 3.2 to Rails 4.

Assets - why aren't they working in a proper way?

No non-fingerprinted asset files versions for you. I've noticed this issue in a really painful way: on the production. It isn't documented anywhere, so I assume, that this is a bug (nasty one btw). When you perform:

rake assets:precompile

It generates whole bunch of files, however you might notice, that there's no non-fingerprinted once there. All of them include fingerprints. I've even tried to disable fingerprinting at all with:

config.assets.digest = false

but Rails keeps ignoring that.

My first reaction after I've noticed that, was like that:

Assets stap

I do like digest idea, but there are some libraries (like Ckeditor) that won't work without "clean" file versions. So until it is fixed, I'll be using a simple rake task that I've created:

  require 'ostruct'

  desc 'Creates a non-digest version of all the digest assets'
  task fix_assets: :environment do
    require 'fileutils'
    regexp = /(-{1}[a-z0-9]{32}*\.{1}){1}/

    assets = File.join(Rails.root, 'public', Susanoo::Application.config.assets.prefix, "**/*")
    Dir.glob(assets).each do |file|
      next if File.directory?(file)
      next unless file =~ regexp

      source = file.split('/')
      source[source.length-1] = source.last.gsub(regexp, '.')

      non_digest = File.join(source)
      File.delete(non_digest) if File.file?(non_digest)

      FileUtils.cp(file, non_digest)

This will go through all the assets and will copy fingerprinted versions to non-fingerprinetd once. It should be executed after assets precompilation:

rake assets:precompile
rake fix_assets


There's whole bunch things that were changed in ActiveRecord:

All method

All method will now return a new relation instead of Array:

# previously:
News.all.class #=> Array

# in Rails 4
News.all.class #=> ActiveRecord::Relation::ActiveRecord_Relation_News

Thanks to that, we can do chainings on an all method.

Load method

Load causes the records to be loaded from the database if they have not been loaded already. You can use this if for some reason you need to explicitly load some records before actually using them. The return value is the relation itself, not the records. You can treat this a bit as a replacement for all method.

None scopes

None scopes are one smart way to handle privileges management for AR resources (but not only for that!). Sometimes we want to create a method, that returns limited amount of objects based on incoming data. In previous Rails versions we would normally return an empty array if we wouldn’t have any privileges. However that might be troublesome when we're chaining scopes:

class Fancy < ActiveRecord::Base
  def self.resources_for(user)
    user.has_role?(:admin) ? all : []

This obviously won't work with chaining (will raise an error):

# Will raise undefined method `active' for []:Array fir bith cases

In Rails4 we can use none scope that will allow us to chain as many scopes as we want. The none scope is implemented with ActiveRecord::NullRelation. No queries will be performed on the database:

class Fancy < ActiveRecord::Base
  def self.resources_for(user)
    user.has_role?(:admin) ? all : none

Now the chaining will work perfectly.

Not query

Let's allow Rails to talk:

News.where.not('title LIKE ?', rejected_title)
News.where.not(title: rejected_title)
# It was in Mongoid for a while and finally we have it in AR also

update in favour of update_attributes

You can use update now instead of update_attributes. No need to worry due: update_attributes will stay with as for a while also.

@news = News.last

# Rails 3
@news.update_attributes(title: 'Rails 3 is quite old')
# Rails 4
@news.update(title: 'Rails 4 is new and shiny!')

Of course they both do the same.

protected attributes are out

Finally! I've never like this idea. It should not be a models responsibility to manage privileges. I will talk about that more in the next part but for know you need to know that Rails 4 moved the parameter sanitization from the model to the controller layer.

ordering for scopes works in a different way


For more details please see this blog post and this github commit!

I won't even try to count how many times I had to create a scope that looked just like a different one but with a different order. Luckily it ends now! Rails 4 ordering changes the order order :-) Until now any new order has been appended as a last one. This caused troubles sometimes:

class Fancy < ActiveRecord::Base
# Let's assume that this is a scope that is used in many, many places
scope :active, ->{ where(active: true).order('created_at ASC') }

I would love to list all the active Fancy objects, but in a different order. I don't want to change that scope, since it is widely used. So what can we do? Probably we would need to create a new similar scope. But not in Rails 4! In Rails 4 orders aren't appended but instead they are prepended, so we can create scopes with default sort order but change it on demand:

class Fancy < ActiveRecord::Base
# Let's assume that this is a scope that is used in many, many places
scope :active, ->{ where(active: true).order('created_at ASC') }

# created_at ascending sort
# SELECT `fancies`.* FROM `fancies` WHERE `fancies`.`active` = 1 \
# ORDER BY `fancies`.`created_at` ASC

# created_at descending sort
# SELECT `fancies`.* FROM `fancies` WHERE `fancies`.`active` = 1 \
# ORDER BY `fancies`.`created_at` DESC, `fancies`.`created_at` ASC
Fancy.active.order('created_at DESC')

First this might cause you a bit of troubles, especially if you're using meta_search or Ransack. You'll need to rewrite most of your search invocations. But in a longer perspective, this change is really good. If you want to pass multiply sorting orders, instead of doing something weird like that:

# This will generate sorting first by title and then by created at
Fancy.all.order('created_at DESC').order('title ASC')

You may want to use this syntax:

# Here order will be from left to right
Fancy.all.order('title ASC', 'created_at DESC')

regexp validation for validates_format_of

After trying to run your Rails app, you may see such an ArgumentError

ArgumentError: The provided regular expression is using multiline anchors (^ or $),
which may present a security risk. Did you mean to use \A and \z,
or forgot to add the :multiline => true option?

If you don't expect multiline incoming data, you need to replace all the "^" with "\A" and all the "$" with "\z". If you expect multiline strings, just specify the multiline: true option. After that, you're ready to go.

auto_explain_threshold_in_seconds is gone

Just remove it from your config file and:


MySQL strict mode

Not sure if it came with Rails 4 - but I like that! If you encounter such an error:

ActiveRecord::StatementInvalid: Mysql2::Error: Field 'seo_url' doesn't have a default value:
INSERT INTO `texts` (`name`, `seo_url`) VALUES ('name')

You need to change your tables and define default values for columns that cannot be null:

change_column :logs, :action, :string, :limit => 255, :null => false, :default => ''

find_or_initialize_by in favour of find_or_initialize_by_attr1_and_attr2

DEPRECATION WARNING: This dynamic method is deprecated.
Please use e.g. Post.find_or_initialize_by(name: 'foo') instead.

It means that instead of:

Post.find_or_initialize_by_name_and_title(name, title)

You should do this:

Post.find_or_initialize_by(name: name, title: title)

Something is wrong when we inherit not directly from ActiveRecord

Well this is not a feature - more like a bug to me. When you inherit from an abstract class that inherits from AR:

class Abs < ActiveRecord::Base
  self.abstract_class = true

class Ebs < Abs
  self.table_name = :ebses

and you try to use such an object, you might get an error:

ActionView::Template::Error: Mysql2::Error: Incorrect table name '': SHOW FULL FIELDS FROM ``

Didn't figure that out yet. Unfortunately I had to do a workaround and I've extracted common functionalities into a module that is included in all the classes that were inheriting from my abstract class.

Update: You can find the solution here: http://stackoverflow.com/questions/27914918/ruby-on-rails-rake-throwing-incorrect-table-name-error-after-updating-rails-pr

In general, just don't declare relations in an abstract class.

Copyright © 2023 Closer to Code

Theme by Anders NorenUp ↑