Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Ruby developers have many great options for simply hosting their web applications. But what happens when your product outgrows Heroku? Managing your own servers can be an intimidating task for the average developer. This session will cover the lessons we've learned at Braintree from building and maintaining our infrastructure. It will cover how we leverage Ruby to automate and control all of our environments. Some specific topics we'll cover: * Orchestrating servers with capistrano * Using puppet for configuration management * Our cap and puppet workflow using git * How vagrant can provide a sane test environment * Some pitfalls you should avoid Help us caption & translate this video! http://amara.org/v/FGaG/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled 'DevOps for the Rubyist Soul', John Downey presents insights from his work at Braintree on managing infrastructure as a Ruby developer. The session addresses the challenges faced by companies as they grow out of simple hosting solutions like Heroku and must begin managing their own servers. Key points discussed include: - **Definition of DevOps**: Downey explains DevOps as a collaboration between development and operations teams, aiming for automation, repeatability, and verifiability, similar to agile development practices. - **Journey Towards DevOps**: Braintree's transition to DevOps involved forming a 'blue team' focused on infrastructure tasks, moving away from purely development work to encompass operational responsibilities. - **Use of Tools**: Several tools were highlighted, including: - **Puppet**: For configuration management, emphasizing how it assists in maintaining server consistency and automating server configuration through Puppet code and manifest files. - **Capistrano**: Used for orchestration alongside Puppet, providing a means to manage server deployment efficiently. - **Vagrant**: A tool enabling developers to create test environments quickly and safely, facilitating ruby development in an environment representative of production. - **Version Control and Git**: The importance of Git in maintaining organized and coherent configurations across environments, utilizing branches for different stages of development (QA, staging, production) was emphasized. - **Best Practices and Lessons Learned**: - Adhering to Puppet's style guidelines. - Using modules effectively for better code management. - Regularly merging changes to avoid conflicts. - Utilizing Vagrant for smoother onboarding processes and development workflows. The session concluded with humorous references to DevOps culture and practices, stressing the significance of communication among team members in avoiding conflicts or overwrites in server configurations. Downey's presentation is a comprehensive guide for Ruby developers aspiring to implement DevOps strategies effectively in their work environment.
Suggest modifications
Cancel
