For all the excitement and talk of cloud it seems the reality, at least in enterprises, is a little less glamorous. With more and more executives backing the move to the cloud, more and more organisations are booting up large migration programmes. Unfortunately their aging IT departments lack the experience required and organisations are forced to depend on service providers to fill the gap.
For the last year or so, the majority of our new projects at Made Tech have used Ansible as our go-to tool for provisioning and configuring our servers with the software that runs on them. We’ve paired Terraform with Ansible and Chef previously for creating our cloud resources, but have recently been experimenting with using Ansible to see if the one tool was capable of both of these stages in our infrastructure setups. We’ve not been disappointed with our experiences so far.
Let’s Encrypt is a new certificate authority which provides free and automated certificates. It’s sponsored by many of major players including the EFF, Mozilla and Google.
Here at Made we’re always trying out new technologies that will automate repetitive tasks we need to perform on each new project.
A pipeline is a set of steps that your code takes to get from a developer’s local machine through to a production environment. This pipeline is managed by a tool that lets you define these steps, what they do, and how and when it proceeds onto the next one.
Continuous Delivery is an approach to software delivery which promotes small incremental releases rather than huge iterations. Every push to master which passes its test suite is considered to be production ready, and as a result our deployment pipeline is optimised to get it out to production websites as quickly as possible, without sacrificing security and safety. This benefits us as developers and our customers in the same ways. New features and bug fixes are deployed rapidly, and code is safer by virtue of having smaller changes. How much can you break in a day or two? We are all spared the anxiety of large, lengthy deploys where weeks of work can be released to production at once.
Otto is marketed as the successor to Vagrant, the development tool that has been used by developers across the globe for the past five years.
I’ve seen quite a few articles recently detailing the steps to creating a simple Ruby on Rails development environment without Vagrant. I’ve found a few issues with these that make the environment somewhat unfeasible for real use. Hopefully, by the end of this article you will have a Docker-based development environment that can actually be used for real development.
We’ve been long-time proponents of PaaS, or Platform as a Service. We’ve also been long-time consumers of IaaS, or Infrastructure as a Service.
You should treat your servers as cattle, not as pets. While we can’t claim to have coined this catchphrase here at Made, it is certainly a philosophy that we subscribe to.