GitHub: Use your code at scale
March 29, 2019
GitHub: Use your code at scale
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with GitHub
Our company used GitHub for the central repository for code with which to build our application, but also as a means for storing data on server makeup and configurations. This data is used by our operations team for server buildouts, patching and configuration changes (which can be distributed across multiple locations), and data centers. The merge process allows us to check in new changes, review code, what has changed for a specific branch but also to revert changes that have been seen to cause problems.
- Merge and review processes make it easy to compare changes and approve.
- A central repository for code allows for many users to access and use for deployment and setup of complex systems.
- Integrations with Chef and Octopus further enhance our ability to grow our infrastructure as needed.
- Getting the formatting of changes or updates correct and pass validation checks can be tricky. We use other third-party software to validate before checking in changes.
- We have been able to grow our infrastructure as scale while keeping a central repository of our configurations.
- All data and code in GitHub has become the source of truth for all team members to refer to.
- A configuration change required to be updated on multiple servers can be quickly updated in GitHub and pushed to all servers with Chef that relies on GitHub as the SoT for all files and configs.
Did not have a lot of say in the choice to go with GitHub, I am a member of the operations team that uses GitHub for our work, but was not involved in the decision making process. As a user of the application, I can say that it has helped us keep consistent configurations across all systems without having to verify all servers are set up the same way. It greatly reduced doubt in making sure a configuration change has been pushed to all servers.