<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ruby on Rails on storck.io</title>
    <link>https://storck.io/tags/ruby-on-rails/</link>
    <description>Recent content in Ruby on Rails on storck.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Feb 2023 11:05:47 +0100</lastBuildDate>
    <atom:link href="https://storck.io/tags/ruby-on-rails/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Validating HTTP(S) URLs in Ruby on Rails</title>
      <link>https://storck.io/posts/better-http-url-validation-in-ruby-on-rails/</link>
      <pubDate>Fri, 10 Jun 2022 16:33:00 +0200</pubDate>
      <guid>https://storck.io/posts/better-http-url-validation-in-ruby-on-rails/</guid>
      <description>Regular expressions are not a great way to validate URLs. Using Ruby&amp;rsquo;s built-in&#xA;URI parser, a custom Active Record Validation Helper can be built to safely&#xA;validate URLs in Ruby on Rails applications while allowing for flexible domain name&#xA;allow-listing.</description>
    </item>
    <item>
      <title>Adding TypeScript to your Svelte components in Rails 6</title>
      <link>https://storck.io/posts/adding-typescript-to-svelte-with-webpacker/</link>
      <pubDate>Tue, 29 Sep 2020 10:28:00 +0200</pubDate>
      <guid>https://storck.io/posts/adding-typescript-to-svelte-with-webpacker/</guid>
      <description>Combine Svelte and Typescript with Ruby on Rails&amp;rsquo; Webpacker to improve your JavaScript workflow and get better feedback in your editor.</description>
    </item>
    <item>
      <title>Moving from Capybara to Cypress</title>
      <link>https://storck.io/posts/moving-from-capybara-to-cypress/</link>
      <pubDate>Fri, 03 Jul 2020 14:51:00 +0200</pubDate>
      <guid>https://storck.io/posts/moving-from-capybara-to-cypress/</guid>
      <description>Cypress makes writing integration tests (or system tests) easier and more fun. This posts shows you the tools needed to add Cypress tests to your Rails application.</description>
    </item>
    <item>
      <title>Deploying Ruby on Rails apps to Kubernetes from Gitlab CI</title>
      <link>https://storck.io/posts/deploying-ruby-on-rails-to-kubernetes-from-gitlab-ci/</link>
      <pubDate>Thu, 11 Jun 2020 12:18:00 +0200</pubDate>
      <guid>https://storck.io/posts/deploying-ruby-on-rails-to-kubernetes-from-gitlab-ci/</guid>
      <description>Gitlab CI allows you to create and manage Kubernetes clusters directly from the interface and easily deploy builds to your existing Kubernets infrastructure. Here&amp;rsquo;s how.</description>
    </item>
    <item>
      <title>Add jemalloc to your Ruby Docker images, now!</title>
      <link>https://storck.io/posts/psa-switch-ruby-docker-to-jemalloc-now/</link>
      <pubDate>Fri, 08 May 2020 10:30:00 +0200</pubDate>
      <guid>https://storck.io/posts/psa-switch-ruby-docker-to-jemalloc-now/</guid>
      <description>&lt;p&gt;The topic of this post is neither new nor original, so I’m going to keep things short. People have been using jemalloc with MRI Ruby for years and praising it’s benefits all the while. The TL;DR here is: for Rails apps, using jemalloc will reduce memory consumption and might increase performance a little.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why&#34;&gt;Why?&lt;/h2&gt;&#xA;&lt;p&gt;To illustrate my own experience, here’s a Grafana graph showing the effect of switching to jemalloc on a production server running a few instances of a Rails application:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Disable JavaScript source maps in production Rails applications</title>
      <link>https://storck.io/posts/rails-webpack-disable-source-maps-in-production/</link>
      <pubDate>Mon, 20 Apr 2020 10:30:00 +0200</pubDate>
      <guid>https://storck.io/posts/rails-webpack-disable-source-maps-in-production/</guid>
      <description>&lt;p&gt;Ruby on Rails 6 allows us to leverage the excellent Webpack bundler to manage JavaScript and CSS components in a way that&amp;rsquo;s more native to those technologies than the old asset pipeline: no more gems to wrap JavaScript libraries and no more libv8 gem issues.&lt;/p&gt;&#xA;&lt;p&gt;Another advantage Webpack brings is the excellent source maps. I was surprised to see the source code of my Svelte components, complete with comments available from the Firefox development tools:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
