Puppet Labs vs Shipit: What are the differences?
What is Puppet Labs? Server automation framework and application. Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Puppet Labs and Shipit belong to "Server Configuration and Automation" category of the tech stack.
Puppet Labs and Shipit are both open source tools. It seems that Puppet Labs with 5.37K GitHub stars and 2.1K forks on GitHub has more adoption than Shipit with 4.71K GitHub stars and 199 GitHub forks.
What is Puppet Labs?
What is Shipit?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Shipit?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Shipit?
Sign up to get full access to all the tool integrationsMake informed product decisions
I'm using puppet to configure my servers. This makes it really simple to ensure that I have the same environment. There is a bit of a learning curve, but the repeatability definitely makes it worth the effort. I found puppet to be a little easier to pick up relative to chef, but I've used both. They're both great solutions.
I really like that there are a lot of modules available on the puppet forge that are being actively maintained.
We provision all servers with puppet. We have one central Puppet server which uses puppet modules referenced by a Puppetfile. Those puppet modules are partly from forge and partly self written.
All modules which are self written, have to be tested using rspec-puppet and beaker.
Opstax uses puppet for role/profile based configuration management and the distribution of small/static code.
Configures or servers and allows us to be region independent we have 5 regions across the globe.