Server automation framework and application
Ruby HTML Shell Emacs Lisp VimL Makefile
Pull request Compare This branch is 2 commits ahead, 710 commits behind puppetlabs:master.
Failed to load latest commit information.
acceptance (maint) Restrict quick test to omit trying to test removed tests May 11, 2016
api Merge remote-tracking branch 'upstream/stable' Mar 17, 2016
autotest (maint) Ensure every file has a trailing newlines Apr 23, 2012
benchmarks (PUP-5482) Add a benchmark to missing type caching Apr 4, 2016
bin (PUP-2563) Exit with 1 on pre-1.9.3 ruby Dec 4, 2014
conf (docs) Update URLs for generated references Mar 18, 2016
docs (maint) Update docs and license with new branding Apr 21, 2016
examples/hiera (Maint) Update commands to use new forms in hiera examples Sep 19, 2013
ext (PUP-3740) Require at least ruby 1.9.3 for the puppet gem Apr 22, 2016
lib (PUP-6253) Update documentation of SemVer and SemVerRange new May 11, 2016
man (PUP-5123) Replace http:// links with https:// Nov 9, 2015
spec WIP: add crude run mode support May 12, 2016
tasks (PUP-1455) Use CFPropertyList to read launchd plists Dec 23, 2015
util (PUP-3912) Update parallel:spec task for rspec 3 Jan 26, 2015
yardoc/templates/default (#18023) Document user facing classes using yardoc and show api. Jan 5, 2013
.gemspec (PUP-5123) Replace http:// links with https:// Nov 9, 2015
.gitignore (PUP-4347) Add test for the File resource ignore attribute May 5, 2015
.hound.yml (maint) Point HoundCI at the existing rubocop config Mar 24, 2016
.mailmap (maint) Update mailmap for git shortlog Oct 18, 2012
.noexec.yaml (#15464) Exclude gem command from bundler Aug 20, 2012
.rubocop.yml (PUP-5545) Rubocop to ignore files in the module skeleton May 4, 2016
.travis.yml (maint) Bump to ruby 2.3.1 in travis ci May 1, 2016
.yardopts (maint) Remove reference to README_DEVELOPER Apr 22, 2014
COMMITTERS.md (PUP-5123) Replace http:// links with https:// Nov 9, 2015
CONTRIBUTING.md (maint) Update docs and license with new branding Apr 21, 2016
Gemfile WIP: spec to illustrate merging/interpolating across hocon files May 12, 2016
LICENSE (maint) Update docs and license with new branding Apr 21, 2016
README.md (maint) Add maintainers section to readme Apr 24, 2016
Rakefile (maint) Update commit rake task to allow revert Aug 20, 2015
appveyor.yml (maint) Skip updating bundler in AppVeyor Mar 2, 2016
install.rb (PUP-5781) Install additional bat files Feb 3, 2016

README.md

Puppet

Build Status Inline docs

Puppet, an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Documentation

Documentation for Puppet and related projects can be found online at the Puppet Docs site.

HTTP API

HTTP API Index

Installation

The best way to run Puppet is with Puppet Enterprise, which also includes orchestration features, a web console, and professional support. The PE documentation is available here.

To install an open source release of Puppet, see the installation guide on the docs site.

If you need to run Puppet from source as a tester or developer, see the running from source guide on the docs site.

Developing and Contributing

We'd love to get contributions from you! For a quick guide to getting your system setup for developing take a look at our Quickstart Guide. Once you are up and running, take a look at the Contribution Documents to see how to get your changes merged in.

For more complete docs on developing with puppet you can take a look at the rest of the developer documents.

License

See LICENSE file.

Support

Please log tickets and issues at our JIRA tracker. A mailing list is available for asking questions and getting help from others. In addition there is an active #puppet channel on Freenode.

We use semantic version numbers for our releases, and recommend that users stay as up-to-date as possible by upgrading to patch releases and minor releases as they become available.

Bugfixes and ongoing development will occur in minor releases for the current major version. Security fixes will be backported to a previous major version on a best-effort basis, until the previous major version is no longer maintained.

For example: If a security vulnerability is discovered in Puppet 4.1.1, we would fix it in the 4 series, most likely as 4.1.2. Maintainers would then make a best effort to backport that fix onto the latest Puppet 3 release.

Long-term support, including security patches and bug fixes, is available for commercial customers. Please see the following page for more details:

Puppet Enterprise Support Lifecycle

Maintainers