I've read Artyom's thesis [1] (nice work BTW if you're reading this) on sling & CI, as well as Bertrand's series of sling dev-ops experiment. I need to start putting together an environment for AWS deployments for sling and I'm wondering if crankstart is still the way forward for automated deployments as opposed to custom launchpad configurations. Basically wondering if this text from the README is still current: "it might be completely changed, abandoned etc.", or if it's any closer to being an accepted component.
I started looking into AWS's code-deploy [2], which looks a lot like the Orchestrator in [1]. I suppose one has to commit to drink the Amazon kool-aid before considering code-deploy, but given that we're pretty far down that road already, it looks attractive for the Orchestrator component. Is anyone else working on any AWS-specific deployment work for sling? -Bruce [1] http://bdelacretaz.files.wordpress.com/2014/09/artyom-thesis.pdf [2] http://aws.amazon.com/codedeploy
