DEV Community: Gonzalo Moreno

Easy toggleable boolean in Ruby on Rails

Gonzalo Moreno — Tue, 21 Jul 2020 18:38:25 +0000

There are occasions where we only have to update an attribute within a Rails model and in this case, change only one boolean from True to False or vice versa. To avoid having to enter the model form, check the checkbox, save and be redirected somewhere, it is easier if you implement a couple of lines of code to support toggle with the benefits of Ruby on Rails.

Scenario

We have a model called Banner which has a boolean called published and we need to provide a easier interface to toggle that boolean from a list of banners

1.- Define a Controller action

We make use of an ActiveRecord::Base method called toggle!

# app/controllers/banners_controller.rb

def toggle_published
  @banner.toggle! :published
end

2.- Define the member route to our new action

# config/routes.rb

# Others routes
resources :banners do
  member do
    post :toggle_published
  end
end

3.- Use Rails unobtrusive javascript to update the value

Suppose we have our index.html.erb file with a list of banners. We have to make sure of 2 things, include the helper dom_id and add a link to our new route using the remote option to do the request throught AJAX

# app/views/banners/index.html.erb

<tr id="<%= dom_id(banner) %>">
  <td class="published">
    <%= link_to banner.published_icon, toggle_published_banner_path(banner), remote: true, method: :post, title: t(:update_published) %>
  </td>
</tr>

4.- Update the DOM with the new content and profit (?)

// app/views/banners/toggle_published.js.erb

$("#<%= dom_id(@banner) %> .published a").html("<%== @banner.published_icon %>")

Ruby + jemalloc on a micro EC2 instance

Gonzalo Moreno — Fri, 27 Sep 2019 05:01:20 +0000

After reading several articles about how badly it manages ruby memory, I wanted to do a test on a small application that I run with Ruby on Rails and Sidekiq to see if there are improvements in the performance of my application on a t2.micro instance (only 1Gb RAM).

So I got down to work and followed the simple steps to move from a Ruby that uses glibc by default to Ruby with jemalloc

First, update and install jemalloc (instructions for Debian/Ubuntu)

$ sudo apt update
$ sudo apt install libjemalloc-dev

Then, reinstall Ruby with jemalloc as option. On my server, I have Ruby 2.5.1 installed, so the command I executed was the following (works with RVM too):

$ RUBY_CONFIGURE_OPTS=--with-jemalloc rbenv install 2.5.1

To ensure that your Ruby uses jemalloc, run the following command:

$ ruby -r rbconfig -e "puts RbConfig::CONFIG['LIBS']"

-lpthread -ljemalloc -ldl -lcrypt -lm

And the results so far…

I expected the RAM used to decrease, but instead, the swap memory decreased

More information

This awesome post

My shiny new personal page

Gonzalo Moreno — Sun, 07 Oct 2018 00:21:57 +0000

After many years of being a developer, I've decided to build my personal page the laziest way, installing Hugo, choosing some template and deploying to AWS S3.

Well, this is not a tutorial at all, I only share my happiness for what has been achieved and looking for tips to improve the content or the user interface

My page is gonzalomoreno.me, was built with Hugo, hosted on AWS S3 and is deployed automatically via Gitlab CI.

Please share your thoughts, good or bad.

Best regards to all