Skip to content

avisheksarkar20/puppet

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

Folders and files

NameName
Last commit message
Last commit date
May 13, 2015
Feb 20, 2015
Apr 23, 2012
Feb 20, 2015
Dec 4, 2014
Mar 18, 2015
Apr 23, 2015
Sep 19, 2013
May 4, 2015
May 13, 2015
Mar 13, 2015
May 13, 2015
Jan 26, 2015
Jan 26, 2015
Jan 5, 2013
May 12, 2015
May 5, 2015
Oct 18, 2012
Aug 20, 2012
Dec 18, 2014
Jan 28, 2015
Apr 22, 2014
May 13, 2013
Mar 18, 2015
Mar 26, 2015
Feb 23, 2015
Jun 3, 2014
Dec 3, 2014
May 1, 2015
Mar 20, 2015

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 97.4%
  • HTML 1.0%
  • Shell 0.9%
  • Puppet 0.3%
  • Emacs Lisp 0.2%
  • Vim Script 0.1%
  • Other 0.1%