Turbo Frames: Faster Rails Interfaces Without a SPA
Jun 28, 26 by Juan Lebrijo about turbojs, ruby on rails, ruby
Modern Rails apps can feel incredibly responsive without adopting a full JavaScript framework. One of the simplest ways to achieve that is with Turbo Frames, which let you update only part of a page after a request.

Imagine a list of articles where clicking "Edit" replaces just the article card with an edit form instead of reloading the entire page.

In your view:
<%= turbo_frame_tag @article do %>
  <h2><%= @article.title %></h2>
  <p><%= @article.body %></p>

  <%= link_to "Edit", edit_article_path(@article) %>
<% end %>
Then, in edit.html.erb:
<%= turbo_frame_tag @article do %>
  <%= render "form", article: @article %>
<% end %>
And in the controller:
def update
  @article = Article.find(params[:id])

  if @article.update(article_params)
    redirect_to @article
  else
    render :edit, status: :unprocessable_entity
  end
end
Because both views use the same turbo_frame_tag, Turbo automatically swaps only that frame's content. Users experience a smoother interface with less bandwidth and fewer full-page refreshes.

Turbo Frames work especially well for:
  •  Editing records inline 
  •  Loading sidebar content 
  •  Pagination within a section 
  •  Dashboard widgets 
If you're building a Rails application and want a more dynamic user experience without the complexity of a single-page application, Turbo Frames are an excellent feature to explore. They embrace Rails conventions while keeping your application fast, maintainable, and enjoyable to build.

Upgrade Ruby and Rails
Mar 24, 26 by Juan Lebrijo about RVM, capistrano, ruby
We have to keep our software updated for security and compatibility reasons. Our Rails systems are managed with RVM, so we can easilly ubgrade ruby. Upgrade Rails is easier because we are using bundler with Gemfile to manage our dependecies.
In local DEV environment should install new ruby and update bundle:
bundle update
rvm install ruby-4.0.1
echo ruby-4.0.1 > .ruby-version
rvm --default use ruby-4.0.1
In the server we should install new version and make it default:
rvm install ruby-4.0.1
rvm --default use ruby-4.0.1
We are using Capistrano and puma for deployment. From local, reinstall puma service: 
cap production deploy
cap production puma:install
Updating Chromedriver when system chrome is updated
Dec 05, 23 by Juan Lebrijo about chrome, Ubuntu, ruby, capybara, blog
I use Capybara for testing, with chrome extension. From time to time Ubuntu asks to update chrome to a newest version. This breaks compatibilty with chromedriver version for testing purposes. You experienced an error like this:
Selection_630.png 23.3 KB
In this link you have all webdriver versions matching with your actual browser version. I downloaded and installed to solve the problem. Here the commands: 
wget https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/116.0.5845.96/linux64/chromedriver-linux64.zip
unzip chromedriver-linux64.zip
sudo mv chromedriver-linux64/chromedriver /usr/local/bin/
sudo chown root:root /usr/local/bin/chromedriver
sudo chmod +x /usr/local/bin/chromedriver
rm -r chromedriver*

Hope it workd for you. Happy coding!!