TMtmountain·Mar 29, 2025
For anyone struggling to manage their PL/pgSQL codebase via migration files. This is a game changer.
https://github.com/t1mmen/srtd
In Postgres Language Server: Initial Releaset1mmen
srtd
TypeScript2025â2025
t1mmen / srtd
srtd
đȘ Supabase migrations made magical: Live-reloading SQL + Sane, reviewable diffs + Maintainable templates = Delightful DX
2Distinct people
4Mentions
0Explicit recommenders
105GitHub stars
What to know before exploring
What it is
đȘ Supabase migrations made magical: Live-reloading SQL + Sane, reviewable diffs + Maintainable templates = Delightful DX
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7âNov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week4 dated mentions
Observed mentions: 2025-01-09 09:58:50 UTC to 2025-03-29 13:20:37 UTC. Weeks start Monday, UTC.
Counts come from the repositoryâs dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 6 | 2025-01-06 00:00:00 UTC | 2025-01-13 00:00:00 UTC | 1 | 1 | 0 |
| Jan 13 | 2025-01-13 00:00:00 UTC | 2025-01-20 00:00:00 UTC | 0 | 0 | 0 |
| Jan 20 | 2025-01-20 00:00:00 UTC | 2025-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2025-01-27 00:00:00 UTC | 2025-02-03 00:00:00 UTC | 0 | 0 | 0 |
| Feb 3 | 2025-02-03 00:00:00 UTC | 2025-02-10 00:00:00 UTC | 0 | 0 | 0 |
| Feb 10 | 2025-02-10 00:00:00 UTC | 2025-02-17 00:00:00 UTC | 0 | 0 | 0 |
| Feb 17 | 2025-02-17 00:00:00 UTC | 2025-02-24 00:00:00 UTC | 1 | 0 | 1 |
| Feb 24 | 2025-02-24 00:00:00 UTC | 2025-03-03 00:00:00 UTC | 0 | 0 | 0 |
| Mar 3 | 2025-03-03 00:00:00 UTC | 2025-03-10 00:00:00 UTC | 1 | 0 | 1 |
| Mar 10 | 2025-03-10 00:00:00 UTC | 2025-03-17 00:00:00 UTC | 0 | 0 | 0 |
| Mar 17 | 2025-03-17 00:00:00 UTC | 2025-03-24 00:00:00 UTC | 0 | 0 | 0 |
| Mar 24 | 2025-03-24 00:00:00 UTC | 2025-03-31 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesYou can greatly improve DX with something like this and get the best of both worlds.
https://github.com/t1mmen/srtd
In The program is the database is the interfacehttps://github.com/t1mmen/srtd might help here. The general idea is to define functions/policies/etc as «SQL templates», your source of truth. The templates built into Supabase migrations.
While developing, srtd can hot/live reload your templates into the local db when changed.
I built this to scratch my own itch, and itâs been working VERY well for us. Huge DX benefits, and itâs made code reviews a LOT easier, since the reviewer can focus on whatâs actually changed.
In A Language Server for PostgresShow HN: SRTD â Live-reloading SQL templates for Supabase migrations
We've been happily building on Supabase for ~two years, two major DX frustrations aside:
1. The iteration cycle for database functions was needlessly complex. Some variation of this workflow was common:
- Find existing function/view/policy/etc in past migrations
- Copy to SQL editor
- Make changes
- Test
- Copy back to migration file
- Repeat
2. Code reviews were painful since every function modification appeared as a complete rewrite. Adding a single line in a 400-line function results in an entirely new file with +401 lines. No historic context, either. Lots of mental overhead for reviewers.
I have searched for tools/workflows to address this, but have came up short. (https://news.ycombinator.com/item?id=36007640, https://news.ycombinator.com/item?id=37755076)
So, over the holidays I paired with Claude to make SRTD (Supaba
Read the rest
se Repeatable Template Definitions), addressing these issues with a template-based workflow:
# Make a template with safely repeatable SQL
echo "-- some idempotent sql" >> supabase/migrations-templates/my_function.sql
# Edit your SQL templates, changes auto-apply to local DB
npx @t1mmen/srtd watch
# Generate standard Supabase migrations when ready
npx @t1mmen/srtd build
Key features:
* Live-reload for SQL templates (great for functions, policies, views, etc)
* Single source of truth for database objects, with history/functional git blame.
* Standard (Supabase) migrations as output
* Safe iteration with WIP templates that never generate migrations (.wip.sql)
Focus has been on Supabase migrations, but it'll work with any Postgres database using `20250109104647_migration_name.sql` formatted migrations with some configuration adjustments.
Happy to accept PR or issues for other migration file formats (or even DBs).
Project: https://github.com/t1mmen/srtd
Would love to hear your thoughts, feedback, and ideas for improvement!