Hi, On Wed, Nov 20, 2013 at 11:49 AM, Felix Meschberger <[email protected]> wrote: > Am 20.11.2013 um 20:08 schrieb Bertrand Delacretaz <[email protected]>: >> ...Due to the async way in which Sling handles config and code changes, >> making sure things happen atomically might require some work. > > Well, if we want to do that we really should investigate Deployment Admin > because this has > transactional promises: Either all or nothing....
Inside of straining too much inside Sling, we might also take a systems approach to this and use throwaway Sling instances. To upgrade to a more recent "config" (including rendering scripts etc) start a new instance, and once it's ready have the front-end switch to it gracefully, like apachectl -k restart does. I've been playing a bit with http://www.docker.io/ and I like what I see - initial experiments at [1] FWIW. Ironing out the "details" would need work, of course ;-) -Bertrand [1] https://git.corp.adobe.com/bdelacre/docker-experiments/blob/master/sling-runnable-jar/Dockerfile
