<![CDATA[Dev Almanac]]>https://blog.vsrinath.devRSS for NodeSat, 16 May 2026 12:01:14 GMT60<![CDATA[Fedora 43 for Rails: Quickstart to a Rails‑Ready Dev Machine]]>https://blog.vsrinath.dev/fedora-43-for-rails-quickstart-to-a-rails-ready-dev-machinehttps://blog.vsrinath.dev/fedora-43-for-rails-quickstart-to-a-rails-ready-dev-machineTue, 07 Apr 2026 05:46:39 GMTThis short guide helps you get a Fedora 43 workstation ready for Rails development. It covers updating your system, enabling repositories needed by AppImages and other third‑party software, and installing a minimal developer toolchain (Ruby support, build tools, PostgreSQL headers, Docker) plus a few useful CLI apps and GNOME extensions so you can start building Rails apps quickly.

Run and install updates

sudo dnf update -y

Enable Terra repo for access to wide variety of packages

sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release

Add packages required for AppImages

https://github.com/AppImage/AppImageKit/wiki/FUSE

Gnome Extensions

Install the gnome-browser-connector to install extensions directly from extensions.gnome.org

sudo dnf install gnome-browser-connector

https://extensions.gnome.org/extension/2645/brightness-control-using-ddcutil/

https://extensions.gnome.org/extension/8675/automatic-theme-switcher/

Terminal Setup

Install Zsh and change shell to Zsh

sudo dnf install -y zsh
grep username /etc/passwd
chsh -s $(which zsh)
grep username /etc/passwd

Install Starship

https://starship.rs/

CLI Apps:

Neovim

sudo dnf install -y neovim python3-neovim

Zoxide: cd command on steroids

https://github.com/ajeetdsouza/zoxide

Atuin CLI: command history search on steroids

https://docs.atuin.sh/cli/guide/installation/

Software Development Tools:

Claude Code

Zed

T3 Code

Firefox extensions:

]]><![CDATA[Macbook Setup]]>https://blog.vsrinath.dev/macbook-setuphttps://blog.vsrinath.dev/macbook-setupSun, 05 Nov 2023 06:46:20 GMTQuality of Life Tools

Developer Tools

Fonts

  • Drafting Mono - I quite enjoy using this as a terminal font

  • 0xProto Nerd Font

  • Dank Mono

  • MonoLisa

CLI Utilities

  • Delta - Brings in fabulous git diff functionality.

  • fd - helps search for files from the terminal

  • ripgrep - faster grep

Browser Extensions

Chrome

  • raindrop.io - fabulous bookmark manager

  • uOrigin Block

Firefox

]]><![CDATA[Rolling back Rails Database migrations]]>https://blog.vsrinath.dev/rolling-back-rails-database-migrationshttps://blog.vsrinath.dev/rolling-back-rails-database-migrationsFri, 15 Sep 2023 10:28:20 GMTI ran into a situation at work where I had to roll back Rails migrations to get my database back into a usable state.

rails db:migrate:status - This shows us the current status of our migrations.

StatusMigration IDMigration
up20350319081542First migration
up20350419081542Second migration
up203504519081542Third migration

rails db:rollback - This lets you roll back one migration at a time.

rails db:migrate:down VERSION=20350419081542 - This rolls back this specific migration file.

]]><![CDATA[How to deploy Rails to Fly.io with Supabase DB]]>https://blog.vsrinath.dev/how-to-deploy-rails-to-flyio-with-supabase-dbhttps://blog.vsrinath.dev/how-to-deploy-rails-to-flyio-with-supabase-dbThu, 02 Feb 2023 17:43:46 GMT

  • Install flyctl command line utility as shown here

  • Sign in to Fly.io by running fly auth login

  • Run flyctl launch from the rails app directory as shown here

    • Remember to answer No when flyctl launch wizard asks if you want to spin up a Postgres DB as part of the launch process since we plan on using Supabase for that.

  • Your app should be would be up, you can verify that in the Fly.io dashboard.

  • Go to Supabase and spin up a database if you've not already done that. Once that DB is up, go to the Database Section of Project Settings, and get the connection String we'll need that later. It'll look something like this:

      postgres://postgres:YOUR-PASSWORD@db.soemthing.supabase.co:6543/mydbname

  • Once you have this we've to make two changes to our current setup.

    • Go to database.yml and make sure the database URL for the production environment points to ENV['DATABASE_URL'] as shown below. We need to do this to make Fly.io take the Supabase DB URL

      •   default: &default
    adapter: postgresql
    encoding: unicode

  production:
    <<: *default
    url: <%= ENV["DATABASE_URL"] %>

    • Now for the final step, we need to add the Supabase DB Connection string as a fly.io app secret. We do that as shown here https://fly.io/docs/flyctl/secrets/

      •   flyctl secrets set DATABASE_URL=postgres://postgres:YOUR-PASSWORD@db.soemthing.supabase.co:66543/mydbname

    • The reason we're setting DATABASE_URL is that Rails Apps automatically connect to the Database specified in DATABASE_URL as mentioned here

    • ]]>