Forking production to dev
I've asked about forking before, I believe in the context of previews. I wanted to raise a specific implementation concept that might make it more feasible (outside of the actual database forking behind the scenes): providing a way to fork production to my dev environment. It would completely overwrite all data, and would be done in a way that preserves all ids, creation time, etc - a literal fork.
I don't know if forking is anywhere on the radar, but if there were a button that could do that I'd press it pretty often to refresh my dev. I find myself doing the real testing in production because the organic result of real usage often just can't be replicated very well.
Implementing this way sidesteps a lot of product questions that might otherwise go into forking, gets some manner of forking shipped in the product, and mostly focuses on just the technical effort of actually forking a convex db.
2 Replies