105 Progress Chef Reviews
Overall Review Sentiment for Progress Chef
Log in to view review sentiment.
I was in deployment department so for every software I need to configure all server manuall like supponse you have many servers that time you don't need to configure you all server just only update on workstation then it will update on all servers another thing is some times yon need to change you ENV variable so that time you can't run you dockesr image for all server instead of these just replace value by suing chef is another best part also for CI/DC part is best Review collected by and hosted on G2.com.
Here is nothing for dislike, but If they provide us containerization with server configuration like dockers with chef that time it will really easy to handle and many people will switch on this Review collected by and hosted on G2.com.
I like the open community with lots of resources present in the documentation and also video tutorials which help someone like me who was new to this technology pick up and complete the tasks assigned easily and effectively . Review collected by and hosted on G2.com.
Compatibility with different programming languages such as python. Review collected by and hosted on G2.com.
The vast variety of receipies in the community. Almost every tool installation has their own recipe. And easy management of central store for receipies. Review collected by and hosted on G2.com.
The configuration tree for the receipe can be bit less complex. Review collected by and hosted on G2.com.
Most of our client uses Chef to deploy new code in an automated fashion. We also use it to update existing configurations and push those changes in an automated fashion to large groups of servers. Having the ability to deploy simple or full system changes out to a large group of servers with little human interaction has been a game changer for our company allowing us to deploy at scale and grow our infrastructure as our company grows. Review collected by and hosted on G2.com.
It is very complex tool and The Chef-client agent needs to be run on the nodes frequently to update the details of it state to master. And also to index the nodes based on tags. Review collected by and hosted on G2.com.
- Great centralized features: data bags (central data storage), encrypted data bags, restricting script (cookbook) version on given nodes...etc.
- Amazing ruby-based syntax. This what makes Chef my preferred configuration management tool over other tools that use their own DSL. You can always use Ruby directly for complex tasks
- Open source: Chef has an open source version that does not lack important features
- Ability to test your Chef scripts (recipes and cookbooks) using automated InSpec tests Review collected by and hosted on G2.com.
- There is some learning curve involved, but it's worth it
- It might be an overkill for simple automations Review collected by and hosted on G2.com.
Once you're familiar with Chef, it's a very powerful tool for ensuring that your servers are all provisioned in the exact same way, and committing those choices to source control. There is a fairly active open source, and a lot of community cookbooks already exist for common tasks. Review collected by and hosted on G2.com.
Reasonably challenging to get up and running with, especially if you aren't coming from a Ruby background. The documentation lags somewhat and I occasionally found myself digging into source code to understand a behavior. Review collected by and hosted on G2.com.
