@mrtoto so each buildname is basically a timestamp ie "20241127102454" - the service is looking in to the folder "current" which is a symlink pointing to the latest build name. A rollback is moving the symlink to the previous build (easy because they are sortable and uniquely named) and restarting the service. We keep at least the last 5-10 build but older ones are also auto cleaned.

@hukl Makes sense. Simple and powerful. A bit like Capistrano did it back in the day (maybe still does?).