I’m able to see my database/tables from within Replit (via Drizzle) while I’m in the repl that created the database. However once I fork the repl, I’m not able to see the db any longer. While I can still read and write to the database from the fork, it is not visible. Any workarounds to this within the Replit environment?
I think fork’s still pull from the same DB in the old repl using the same db credentials.
Tell Agent to clone the original DB into the new fork. Then you’ll work on separate DB’s.
That’s a good idea. Just create a clean database with all the same data so I can test functionality and see the tables etc. thank you.
You’ll need to specify to create a clean db or copy the current db including content.
Either way has worked well for me in the past.
1 Like
Is this in docs? If not, it should be, I think there’s been a few of us that have ran into this issue before. I think this is a good workaround when forking, what happens when you merge? Do you manually have to deprovision the new databases or how do you handle that?
My apologies, I was referring to the process when remixing/duplicating a project in Replit, not git forks.
So I guess I saw those options as Replit’s unique git-style nomenclature, so that’s what I meant. Does remixing operate differently than that?
If not, curious on what you do with the db after merging the remix back into the original project.
I’ve never done it tbh, I usually will split off before a big feature, feature usually works and I keep it and never go back.