Yes, in the Pharo world there are coredumps, logs, serialization of the context of the exception (so you can open a debugger later from another host and see the

Yes, in the Pharo world there are coredumps, logs, serialization of the context of the exception (so you can open a debugger later from another host and see the messages walkback and inspect the values of all objects and its instvars on any step of that wallback), also I've made a RESTful REPL [1] to interact live with headless images and I'm cough secretly working in websocket based IDE. For the rest I can tell you that: - The CI doens't have anything special in it, just build and delivers, after many categories of tests, a docker image with the app ready for production. - Iceberg for a shared repo. Devs usually use one fresh image per new branch to work on. Flow is reasonably approximated to git-flow. - The app is generally architected as stateless as it can be so it can enjoy undefined horizontal scaling capacity. [1] https://github.com/sebastianconcept/REPLEndpoint https://github.com/sebastianconcept/REPLEndpoint