Skip to content

kylog/puppet

This branch is 12010 commits behind puppetlabs/puppet:main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

author
LuvCurves
Oct 14, 2016
68873c0 · Oct 14, 2016
Oct 14, 2016
Sep 27, 2016
Apr 23, 2012
Apr 4, 2016
Dec 4, 2014
Mar 18, 2016
Apr 21, 2016
Sep 19, 2013
Aug 31, 2016
Oct 14, 2016
Nov 9, 2015
Oct 14, 2016
Dec 23, 2015
Jul 7, 2016
Jan 5, 2013
Jul 9, 2016
Aug 17, 2016
Mar 24, 2016
Oct 18, 2012
Aug 20, 2012
May 4, 2016
Jul 8, 2016
Aug 23, 2016
Nov 9, 2015
Apr 21, 2016
Jul 28, 2016
Apr 21, 2016
Sep 27, 2016
Sep 6, 2016
Sep 16, 2016
Jul 27, 2016
May 20, 2016

Repository files navigation

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

About

Server automation framework and application

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Ruby 98.2%
  • HTML 0.9%
  • Shell 0.7%
  • Emacs Lisp 0.1%
  • Vim Script 0.1%
  • Makefile 0.0%