RubyFlow The Ruby and Rails community linklog

Submit a post

You can use basic HTML markup (e.g. <a>) or Markdown.
Note that your post may be edited to suit the format of the site.

As you are not logged in, you will be
directed via GitHub to signup or sign in

Post Preview

Note: Only the first pargraph is shown on the front page and overly long paragraphs may be broken up.

Today

Shrinking a 130 GB Postgres to a Local Copy with Greenmask: What Worked and What Brok

https://rubyinsights.blog/en/blog/shrinking-a-130-gb-postgres-to-a-local-copy-with-greenmask-what-worked-and-what-broke

Staging had grown past 130 GB, a full pg_dump was out of the question, seeds never reproduced real bugs, and the data was full of PII. This post walks through building a small, FK-consistent, masked subset of a Rails app’s Postgres with Greenmask. It covers virtual references for Rails associations that never got a database FK, and masking every user to user<ID>@example.test with a known dev password. It also goes through the six things that broke and how each was fixed: NULL-owner rows slipping through, a self-referencing FK that panics the planner, invalid SQL from polymorphic references, orphan rows, the source running out of temp space on a 70 GB table, and a PostGIS NOTICE that aborts the restore. The result is a repeatable pipeline: restore by section, run a repair pass before the FKs are created, then verify.

Wilbert Ribeiro  
 Discuss

Don't bet on SELECT's order: shuffle your rows and see what folds

https://evilmartians.com/chronicles/dont-bet-on-select-order-shuffle-your-rows-see-what-folds

SELECT * FROM posts carries no promise about the order of the returned posts. Yet, every relational database hands them back in some order, and code and tests start depending on that order. You can’t grep for a bug like this, but you can smoke it out by deliberately shuffling the rows of every unordered query and seeing what fails. (Rails has since merged a switch of its own from Evil Martians, config.active_record.shuffle_unordered_selects, due in 8.2.) We also share pg_disorder, the open-source PostgreSQL extension we built to do the same thing at the database level. Read more

Travis-Turner  
 Discuss

Brunch Gem: Isolated Development Environments for Git Branches and Worktrees

https://dev.to/ciembor/brunch-gem-isolated-development-environments-for-git-branches-and-worktrees-4n38

Brunch is a Ruby gem that gives Git branches and worktrees isolated development environments. Each branch can have its own containers, network, volumes, and persistent state, while each worktree gets its own host port. This makes it easier to switch between branches safely and to run multiple worktrees in parallel, including workflows driven by IDEs and coding agents. Read more

Maciej Ciemborowicz  
 Discuss

Billing in Rails 8 — a practical guide to Pay + Stripe

https://robrace.dev/billing-in-rails/?utm_source=rubyflow&utm_campaign=launch

I just released Billing in Rails 8, a 126-page implementation guide for building subscription billing into a Rails app with Pay and Stripe. It focuses less on getting the first Stripe Checkout session working and more on everything that comes after: keeping provider state separate from product behavior, stable application-level plans, entitlements and limits, trials, upgrades and downgrades, cancellation, failed payments, reconciliation, and testing the whole thing without making Stripe your application architecture. Read more

polysaturate  
 Discuss

Rails World '26: The RubyGems Compact Index

https://go.fastruby.io/d58

Every time Bundler resolves your Gemfile, it’s talking to the compact index. In this post, the speaker walked us through what the compact index actually is, how RubyGems.org keeps it in sync at scale, and two features Jenny helped ship in the past year to make gem installs faster and more secure. Read more

Ernesto Tagwerker  
 Discuss
Next page »
Loading older posts