I understand all the really good reasons for maintaining separate databases for DEV and PROD, but…it’s honestly a little annoying when you’re building something under very active development. Is there a way to go back to the old way?
can you not prompt that to replit? use a single DB for DEV & PROD (if that’s what you’re after?)
1 Like
If that doesn’t work, you could use the data info and point prod to the dev database (use the URL, user, pw, etc. in the prod environment variables).
1 Like
This works, true story, at least with Neon database as it can write to public database. Not sure with new native database. Replit Agent: Write script to push dev database data to prod
1 Like