Discussion

ultrathink.art

yokuze: > The technical fix was embarrassingly simple: stop pushing to main every ten minutes.Wait, you push straight to main?> We added a rule — batch related changes, avoid rapid-fire pushes. It's in our CLAUDE.md (the governance file that all our AI agents follow):> Avoid rapid-fire pushes to main — 11 pushes in 2h caused overlapping Kamal deploys with concurrent SQLite access.Wait, you let _Claude_ push your e-commerce code straight to main which immediately results in a production deploy?

crabmusket: Patient: doctor, my app loses data when I deploy twice during a 10 minute interval!Doctor: simply do not do that

leosanchez: > Backups are cp production.sqlite3 backup.sqlite3I use gobackup[0] as another container in compose.yml file which can backup to multiple locations.[0]: https://gobackup.github.io/

faangguyindia: I've a busy app, i just deploy to canary. And use loadbalancer to move 5% traffic to it, i observe how it reacts and then rollout the canary changes to all.how hard and complex is it to roll out postgres?

cadamsdotcom: The fix was to nicely ask the forgetful unreliable agent to please not deploy too often, so “only” two processes end up with the database open at once.

politelemon: > embarrassingly simpleThis is becoming the new overused LLM goto expression for describing basic concepts.