DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > Merging Git Workflow With Puppet Environments

Merging Git Workflow With Puppet Environments

Mitch Pronschinske user avatar by
Mitch Pronschinske
·
Nov. 09, 11 · DevOps Zone · Interview
Like (0)
Save
Tweet
8.05K Views

Join the DZone community and get the full member experience.

Join For Free
If you're trying to keep your development team from doing accidental pushes of incorrect code, a short tutorial on how to use Git, Puppet, and some other open source utilities should go a long way in helping junior sysadmins or sysadmin developers with this kind of problem.  The tutorial comes to you from Puppet Labs:

One of the features offered by Puppet is the ability to break up infrastructure configuration into environments. With environments, you can use a single Puppet master to serve multiple isolated configurations. For instance, you can adopt the development, testing and production series of environments embraced by a number of software development life cycles and by application frameworks such as Ruby on Rails, so that new functionality can be added incrementally without interfering with production systems. Environments can also be used to isolate different sets of machines. A good example of this functionality would be using one environment for web servers and another for databases, so that changes made to the web server environment don’t get applied to machines that don’t need that configuration.  --Puppet Labs

This development model should give deployment managers the simple access control they need to generate new environments, test code, and deny access to change the production environment. This process will take advantage of a neat little tool called gitolite.

Source: http://puppetlabs.com/blog/git-workflow-and-puppet-environments
Git Software development workflow

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • What Is URL Rewriting? | Java Servlets
  • Checklist for API Verification
  • Which JVM Version Is the Fastest?
  • How to Submit a Post to DZone

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo