Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

puppi

Installs and configures Puppi
Project URLRSS FeedReport issues

2,970,952 downloads

182 latest version

1.9 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

  • 3.0.0 (latest)
  • 2.2.11
  • 2.2.9
  • 2.2.6
  • 2.2.5
  • 2.2.4
  • 2.2.3
  • 2.2.2
  • 2.2.1
  • 2.1.14
  • 2.1.13
  • 2.1.12
  • 2.1.11
  • 2.1.10
  • 2.1.9
  • 2.1.8
  • 2.1.7
  • 2.1.6
  • 2.1.5
  • 2.1.3
  • 2.1.2
  • 2.1.1
  • 2.1.0
  • 2.0.8
  • 2.0.0
released Nov 29th 2012

Start using this module

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

Add this module to your Puppetfile:

mod 'example42-puppi', '2.0.8'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add example42-puppi
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install example42-puppi --version 2.0.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
Tags: application, deployment, example42, cli, puppi

Documentation

example42/puppi — version 2.0.8 Nov 29th 2012

In this directory you find some examples of deploy procedures for general purposes deploys (single wars, single files, tarballs, list of files from a list...) described in a single define.

They are made in order to be generic enough to adapt to different environments and scenarious but you might need to design your own deployment process.

In order to do that you can create a new define that includes:

  • All the variables, required or optional, you may want
  • One puppi:project statement
  • All the puppi::deploy statements you need (each one runs a command)
  • All the puppi::rollback statements you need
  • One or more puppi::report statements for reporting

The examples provided here make use of the scripts provided in puppi/files/scripts and tend to split the deploy procedures in many different, reusable, scripts (one gets the source file(s), another archives the current content, another one actually copies the files to deploy and so on) but you can use just a single new script or whatever combination you might prefer.

The default puppi scripts and the general ordering of commands execution in these sample deploy defines follow this scheme: Priority - Kind of operations 1x - Pre Deploy checks 2x - Files retrieving and preparation 3x - Operations to accomplish before the deploy (Archiving, Services stopping..) 40 - Deploy.sh - The script that actually copied the files on deploy dir 4x - Operations to accomplish after the deploy (Services start...) 8x - Post Deploy checks