Let’s charitably say you can run your app with a 1GB cut down snapshot of production.
You’re going to do what, save a snapshot of the database for every commit? Every schema migration?
…and then provision that up in a running database server… which is notoriously not container friendly…
? It doesn’t sound very plausible to me.
Our database is ~1TB, and the app runs with maybe a 10GB cut down version of it, which is a pain in the ass to deal with, just for example, for local dev environments.
I agree with the parent post; it’s cute, but I can’t imagine historical per commit deployments being useful for me, honestly.