Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

skel

An extremely opinionated template aligned to how I module
Project URLRSS FeedReport issues

9,488 downloads

7,083 latest version

4.6 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

  • 0.1.8 (latest)
  • 0.1.7
  • 0.1.6
  • 0.1.5
  • 0.1.4
  • 0.1.3
  • 0.1.2
  • 0.1.1
released Apr 1st 2016
This version is compatible with:
  • Puppet Enterprise >=2015.2.0 < 2016.1.0

Start using this module

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

Add this module to your Puppetfile:

mod 'ncorrare-skel', '0.1.8'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ncorrare-skel
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ncorrare-skel --version 0.1.8

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.

Download

Documentation

ncorrare/skel — version 0.1.8 Apr 1st 2016

skel

Build Status

Table of Contents

  1. Overview
  2. Setup - The basics of getting started with skel

Overview

This is just a boilerplate module that includes testing and automatic deployment to the forge.

Setup

Setup Requirements OPTIONAL

You need to create (using travis encrypt, from the travis gem) to create the following secure environment variables:

  • GITHUB_SECRET_TOKEN
  • BLACKSMITH_FORGE_USERNAME
  • BLACKSMITH_FORGE_PASSWORD

and set up USENETWORK to true and DEPLOY to true in order for deployment to work.

Remaining information is popuplated from Travis environment variables.

Beginning with skel

Create a branch, and after doing a PR it will test and merge automatically if tests work. If DEPLOY is set to true it will tag, change metadata.json, commit, push, build and deploy to the forge