hey guys! i just outlined an idea for making upstream pgflow core and migrations work outside Supabase: pgflow-dev/pgflow#665
@cpursley would love your input, as you are already building this Elixir port on a much more Supabase-decoupled stack.
from the README it looks like this project already works with plain Postgres + pgmq, and even has own migration/stamping approach. im curious if you have ideas from that work which could help upstream, or if im missing some Supabase dependency here.
if i implement #665 upstream, would you guys be interested in adopting the same portable SQL/migration approach so both implementations stay compatible outside Supabase too? thoughts? 🙂
hey guys! i just outlined an idea for making upstream pgflow core and migrations work outside Supabase: pgflow-dev/pgflow#665
@cpursley would love your input, as you are already building this Elixir port on a much more Supabase-decoupled stack.
from the README it looks like this project already works with plain Postgres + pgmq, and even has own migration/stamping approach. im curious if you have ideas from that work which could help upstream, or if im missing some Supabase dependency here.
if i implement #665 upstream, would you guys be interested in adopting the same portable SQL/migration approach so both implementations stay compatible outside Supabase too? thoughts? 🙂