Forge Home


A module to deploy any number of Wintermsith sites


7,568 latest version

4.1 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.0.0 (latest)
released Jan 16th 2016

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'brainsware-wintersmith', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add brainsware-wintersmith
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install brainsware-wintersmith --version 1.0.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



brainsware/wintersmith — version 1.0.0 Jan 16th 2016

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with wintersmith
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module


This module helps install wintersmith and maintain any number of wintersmith sites.

Module Description

This module depends on nodejs to install wintersmith, and vcsrepo to actually checkout your blog!


include wintersmith


after that, we can define a blog:

wintersmith::site { 'blag':
  ensure => 'latest',
  source => 'git://',
  target => '/srv/web/blag.esat',


wintersmith class

package_name Package name of wintersmith. (Default: wintersmith)

package_ensure Ensure wintersmith package is installed (or uninstalled or in a specific version. (Default: present)

path Default Exec path (where to find the wintersmith binary) (Default: /usr/bin:/bin:/usr/local/bin)

wintersmith::site defined type

ensure Ensure vcs is present (or absent, or latest). (Default: present)

source source URI to the vcs repository. (This parameter must be set)

target target dir where to put the vcs repository. (This parameter must be set)

vcs_provider VCS provider. (Default: git)

vcs_revision VCS revision. (Default: master)


Tested on Ubuntu. If vcsrepo, and npm runs on it, and you can adapt the path, it should on run on your OS!


Fork, branch, patch, pull request, etc.