hello, idk what "deploying" means in your case. but in general: try to keep the old deployment online as long as possible and switch to the new one after vali

hello, idk what "deploying" means in your case. but in general: try to keep the old deployment online as long as possible and switch to the new one after validating it ... eg. 1. deploy to a new lets call it "location" - which could be a new directory, a new set of container-images, versioned packages for your linux distro (service managed by systemd) etc... 2. run & validate the newly deployed service-version 3. switch - by certain means, heavily depended on your setup this should keep the downtime within fractions of a second - if this is feasible for your application. but in the end a viable solution depends on your actual deployment-process :) just my 0.02€