Show Us Your Ruby Setup

Community
1

We’d like to see how everyone is working with Ruby. Share a quick overview of your setup:

  • OS
  • Editor / IDE
  • Ruby version manage
  • Terminal
  • Other dev tools

Feel free to add anything else that makes your workflow smoother. Screenshots and short lists are welcome.

1 Like
2
  • OS: Mac
  • Editor / IDE: Zed
  • Ruby version manage: rbenv
  • Terminal: iTerm
  • Other dev tools: GitHub Desktop (nice way to review code and build commits)

I just found the collaborate feature in Zed. I’m working with a colleague that uses a vim plugin, and I’m not vim-fluent. But it seems like the Zed collaboration solves the problem. Giving it a test run today.

1 Like
3

linux / neovim / rbenv / ghostty
other: zsh, git, claude code, obsidian, firefox.

Honestly I can do basically everything I want with a computer that has just those apps.

2 Likes
4

In case it helps, here’s my entire macOS Configuration which I’ve been maintaining for the past decade. It’s all shell scripts but ensures I can rebuild any machine with all of my tools, preferences, settings, etc. You can always pilfer (or clone) for your own setup.

3 Likes
5
  • OS: mac
  • Editor: neovim
  • Ruby version manager: mise (but I’ve started testing rv too)
  • Terminal: zsh (with magus dotfiles and tools)
  • Other: Homebrew, VS studio, Docker, Postman
6
  • OS: Mac
  • Editor: Zed
  • Version management: mise
  • Terminal: Alacritty with tmux, but trying out Ghostty lately. Fish shell.
  • Other: Conductor for running multiple agents
7
  • OS: MacOS
  • Editor / IDE: Vim / RubyMine
  • Ruby version manage: rbenv
  • Terminal: Ghostty 👻
  • Other dev tools: lazygit, claude
8
  • OS: KDE Fedora 44
  • Editor / IDE: Neovim
    • Plugins:
      • vim-test
      • fzf-lua
      • nvim-lspconfig
      • vim-ruby
      • FTerm
    • Theme: navarasu/onedark.nvim
  • Ruby version manage: asdf
  • Terminal: Wezterm
  • Other dev tools:
    • tmux
    • git
    • bash
    • docker
    • syncthing

It’s a pretty simple setup but it works well for me.

Screenshot_20260411_122413
Screenshot_20260411_1224131210×1058 114 KB

1 Like
9

  • OS - Linux: Ubuntu, Arch

  • Editor / IDE - Emacs with evil mode mode key bindings, neovim occasionally

  • Ruby version manage - rbenv

  • Terminal - Kitty, Foot

  • Other dev tools - rubocop, brakeman, bundleraudit, magit, codex

3 Likes
10

OS : OS X
Editor: TextMate
Ruby version manager : RVM
Terminal : Terminal.app
Other dev tools : vagrant, sequel pro

1 Like
11

OS: Mac
Editor / IDE: Sublime Text / RubyMine
Ruby version manage: mise
Terminal: iTerm

Other dev tools: SourceTree, Insomnium

12
  • MacOS Tahoe
  • Zed
  • RVM
  • iTerm
  • Not need to much :joy:
1 Like
13
  • OS: Mac
  • Editor: Zed
  • RVM
  • Ghostly
  • mermaid, JsonCrack, notion
2 Likes
14

TIL about JsonCrack… Thanks! :+1:

1 Like
15
  • OS: Linux (with minimal pain), though Mac sometimes
  • Editor: neovim. Minimal plugins and special configuration. Ctrl-N get go a very long way for completion without any fancy tools.
  • Languages: everything is inside Docker. I am done with version managers and hope to never have to use one again. Docker dev environments have allowed me to switch OSes with zero issues, upgrade my mac with zero issues and never track down why installing a new version of Ruby is yet again broken because of OpenSSL
  • LSP: Got it working, but then it stopped working, it’s not debugable, I forgot about it, and everything is fine. I guess I should try it again.
  • Terminal: Ghostty. Only reason I’m using it is to have the same terminal setup on Mac and Linux. Terminal.app is perfectly fine.
  • Version Control: almost entirely git command line, but I use tig for creating commits. Using delta for diffs on Linux
  • Still using GitHub
1 Like
16

  • OS : chromeos with linux environment enabled

  • Editor / IDE : vscode

  • Ruby version manager : rbenv

  • Terminal : bash

  • Other dev tools : claude free & gemini pro

17

  • OS: iPadOS, macOS, Asahi Fedora GNOME Linux (I bounce between three machines)

  • Editor / IDE: self-hosted code-server for iPad access, Zed on Mac & Linux (see below)

  • Ruby version manage: rbenv, but migrating to rv

  • Terminal: Shellfish on iPadOS, iTerm on Mac, whatever’s default in GNOME these days

  • Other dev tools: I use Solargraph LSP extensively and write YARD comments to type method signatures and variables, plus Rubocop with a custom Bridgetown configuration.

    • Most of my OSS is now hosted on Codeberg…using GitHub as little as possible these days.

I’ll also mention the reason I can switch between iPad/Mac/Linux computers is all my dev stuff is hosted in a cloud VPS (also running Fedora). Even when using my desktop computers using Zed, I’m remoting into the VPS. I don’t have any “local” dev setup. This architecture has worked incredibly well for me now for over a year. Any future computers I purchase, I don’t have to worry about any dev setup because it’s not running directly on the computer. :smiling_face:

3 Likes
18

* OS: Linux Mint and Slackware (mint on my main PC and sw in my travel laptop)

* Editor / IDE: Cursor (corporate mandated) and RubyMine in personal projects

* Ruby version manage: asdf

* Terminal: kitty :cat:

* Other dev tools: dbeaver (I don’t like jetbrains database client), rsync between my two pcs, redis insight, kibana

1 Like
19

DBeaver is awesome (IMO); UX may need a bit of “love”, although I cannot complain in any way… it’s free (community edition) and has been really useful.

1 Like
20
  • OS: Linux (I do use Mac too, but not really for Ruby stuff)
  • Editor: Emacs, sometimes Zed
  • Version manager: mise
  • Terminal: Kitty, fish or zsh, depending on the machine (would like to unify on fish though)
  • Other: really want to get fluid in jj
2 Likes