Just in time for the Node Knockout, I'm happy to announce preliminary support of Node and npm in the master branch of Blueprint.

For the uninitiated, installing Blueprint is easy:

git clone git://github.com/devstructure/blueprint.git
cd blueprint
make && sudo make install

Creating a blueprint of a server and generating shell code that can be used to configure the production server the same way is likewise easy:

blueprint create -S knockout
# Run knockout.sh in production.

If you're new, check out the Blueprint tutorial while you're getting started.

The details are on the blueprint-users mailing list post but the short version is to use Chris Lea's PPA (node.js or node.js-devel) to install Node itself and everything else will work out just fine.

Happy hacking!

Those of you that are fans of RedHat, CentOS, or Fedora are in for a
treat today: 3.0.8 is all about you.

This release closed only three bugs (one of which it caused along the
way!) but made 1000 additions and 173 deletions and made first run on
RPM-based systems on the order of 1000 times faster.

Compare: https://github.com/devstructure/blueprint/compare/v3.0.7...v3.0.8
Tree: https://github.com/devstructure/blueprint/tree/v3.0.8

Functionally, nothing much has changed, so keep on keeping on.

Big news, the 3.0.7 release of Blueprint now includes the blueprint-push and blueprint-pull commands, previously part of Blueprint I/O.  We decided to roll these commands into the main release for simplicity and exposure. Additionally, this release closed 13 issues and contains 42 commits.  

Highlights include:

• Commands for looking inside blueprints, with an eye towards scriptability: blueprint-show-sources(1), blueprint-show-files(1), blueprint-show-packages(1), blueprint-show-services(1), and blueprint-show-ignore(1).  These make it far easier to understand what's being included in blueprints without having to squint at raw JSON.
• A command for interacting directly with blueprints stored locally in Git: blueprint-git(1).
• Blueprint is now less aggressive about using sudo in blueprint-apply(1) in order to play nicely with non-interactive invocations.  Keep using sudo yourself if that's typically how you gain root access.

Updated packages are on packages.devstructure.com and PyPI.  Let us know if you have any questions. Enjoy!