- Building
Build Log · Nov 18 , the main problem: The deploy passed. Where did the orders go?
We built Serendipity as a hackathon demo, then opened a real Mystery Box shop for Stanford students on Nov 18th. Once people started paying through Venmo, our order dashboard became the link between a payment and a delivery. REAL customers started ordering on the first day it was deployed!! Yayy!
But then, to fix and add a few new features, we had to redeploy again. On Nov 18th morning, we were informed by the customers that they can’t see the orders on their dashboards anymore. When we click into our backend, some earlier orders disappeared from the dashboard even though their payments were still in Venmo.
What happened was that Serendipity stored orders in a local JSON file. Our Render service had no persistent disk, so replacing the running instance could wipe that file. The new version went live successfully, and the storefront still looked fine. We only noticed the problem when we went to fulfill orders.
We organized to reproduce it safely. On a test service without persistent storage, create a test order and confirm it appears in the admin dashboard. Redeploy the same code, then check that order again. If the app writes to the instance’s temporary filesystem, the new instance starts without that order.
Loading