Sprinkle, the new provisioning tool I recently released has been progressing really well over the past few months. Its been great to see the focus of Sprinkle to succinctly describe software installation via an elegant Ruby DSL language improve so well.
Last Thursday at our monthly Melbourne Ruby User Group meetup, I had the pleasure of demonstrating Sprinkle to the local community. I've uploaded the slides for those interested:
Gem packages for Sprinkle are available from both GitHub and Rubyforge, and include several new features that have been added sine my original post about the project.
Deployment/command delivery
Support for Vlad in addition to Capistrano, allowing you to leverage upon your existing Vlad configuration
Direct or gateway tunneled net/ssh connection support, allowing you to configure Sprinkle to communicate with remote hosts via net/ssh directly if you desire
Support for provisioning your local machine using Sprinkle by running any commands locally
Installers
Support for automatically verifying installations pre- and post-install to detect any installation errors, and also to optimize the installation order to skip packages already installed.
Support for installing build dependencies of APT packages
Support for installing RPM packages
Support for installing GEM packages from a specific remote repository (eg. github) and into a specific local repository
Documentation
Full RDoc coverage across all classes, also published online
New blog posts & screencast demonstrating Sprinkle
Examples
- Many new examples have been contributed showing several ways of using Sprinkle to provision packages from Git, Ruby, Rails, Sphinx, through to Phusion, etc.
Plus many other contributions from people around the world helping with specs, bugs and other improvements which has been great.
I'd really like to thank everyone who has jumped in and helped with the project in any way over the past few months, I really appreciate your support!
SlideShare document seems broken or private.
Thanks Nic! the presentation was marked as public but I’ve set it again which seems to have fixed it. Should be ok now.
Cheers,
Marcus
Wow, nice idea, and nicely implemented.