Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityTop Con
•••Top Pro
•••
Top Con
•••
Top Pro
•••Top Pro
•••Top Pro
•••Top Pro
•••Top Pro
•••
Top Pro
•••RickZeeland's Experience
Top Con
•••
Puppet forge has Forge for modules, Chef has Marketplace for recipes Both repositories contain a lot of high quality modules/recipes that one can use straight out of the box. Ansible has Galaxy, but amount and quality of play books there does not compare to the above tools. Hopefully this will change in the future as tool matures See More
Ansible is very easy to customize. It doesn't force you to use a language with which you are unfamiliar. Instead, all commands are packaged into YAML modules which are called playbooks. So as long as you use a programming language that can output JSON, you are able to customize it. See More
Terraform is good with declaring and making a new infrastructure, but not great at detecting out-of-band changes or importing existing infrastructure. For example, if you make a change in the AWS console, that might be overwritten or not detected by Terraform, so the "declarative" abstraction can leak. See More
GitLab's UI is clean and intuitive. Each view is designed to not fill the screen with useless information. It displays the activity in a feed-type way in the most prominent part of the view. On top of that, there's a toolbar with buttons which can filter this feed by pushes, merge events or comments. On the left, there's a menu that displays all the links that take you to the different views. For example, a file directory which displays all the files in that repo, a commit view which displays all the commits in cronological order, a network and a graph view that display important information graphically etc... All these details make GitLab's UI extremely intuitive and easy to use, no view is overflown with information and every view displays only the most useful and crucial information needed at that time. See More
Salt works around a Salt master which has multiple agents (Salt minions) that have a persistent connection to the master. Because of this persistent connection, commands to the master are fast to reach the minions. Furthermore, the minions also save various data to the cache in order to make execution faster. When compared against other tools to run the same actions, Salt almost always completes the actions in significantly less time. See More
Chef has a relatively large community. One of the reasons for it is the fact that it's a pretty old and mature tool. Chef, originally released in 2009, is a more mature product. Being popular and with a large and dedicated community means that Chef has lots and lots of resources and guides from third party sources out there for beginners to pick up. Not only that, there are also many plugins and configuration recipes made by the community. See More
Chef was released in 2009, which is relatively a long time ago for software. Since then it has been through several versions and many bug fixes and tests. All of this can make Chef more appealing to teams who are looking for stability and maturity, which are things that Chef brings on the table. See More
Non-expert users can define parameters in a central interface, and Rudder will automatically make sure that IT services are installed, configured, running and in good health. All actions (checks, warnings, fixed errors) are reported immediately in the user interface, keeping drift from nominal behavior low. See More
You define the state the server should be in and Puppet transforms it that state. This is opposed to explicitly declaring a list of actions to be performed. If a developer wants more flexibility and control there's always the option of falling back to explicitly running commands but that's discouraged. See More
Configuration management and automation framework written in C, free for up to 25 hosts. See More
The TeamCity plugin fails the build for all ASP.NET Core applications stating that it is vulnerable to DOS attacks and that "there is no fix available". It is possible however to check the option "do not fail the build" under "advanced options", the report will still be visible under the Snyk Report tab. See More