Continuous Deployment for Firebase using Semaphore

This is a guest post by Abe Haskins, a Firebase engineer at Google. For the past five years, Abe has been helping engineers build Firebase-powered things to help them take over the world.

Firebase has you covered when it comes to building and architecting your app, but what about deploying your projects onto Firebase? Until now that’s been a manual process done via firebase-tools (the command-line interface for Firebase), but now we can use the power of Semaphore to create an entirely automated continuous deployment process.


The Node community is constantly expanding and enterprises are adding it to their stacks, because they can use the same language throughout the entire stack. This year, the Node.js Foundation released the results of a survey which identified how and on which projects people use it. One thing they haven't covered are the versions of Node.js used in projects, which we'll do in this post. This is our our third annual analysis of Node.js versions used in projects on Semaphore's hosted CI/CD service.

Node.js versions used for new commercial projects on Semaphore in 2017


The Ruby community is famous for fast development of greenfield projects and quick acceptance of new concepts. However, it's worth noting that a lot of mature projects such as GitHub, Shopify and Basecamp also operate with Ruby at their core. Every year we take the opportunity to check which versions of Ruby are used for building real-world applications. The data is based on private projects which are tested and deployed on Semaphore's hosted CI/CD service.

Ruby versions used for new commercial projects on Semaphore in 2017


Continuous Integration with Docker Compose

This is a guest post by Nigel Brown, an independent Docker specialist who writes, teaches, and consults on all things Docker-related. Based in the UK, he travels regularly, and can be found at, and on GitHub.

If you take heed of any of the many reports relating to cloud-native computing, then you'd be forgiven for thinking that every organization, large or small, is well on the way to a microservices-oriented application nirvana. The truth is, of course, that a good number of organizations have started the journey, but still maintain traditional monolithic applications, and have some way to go in the journey. Is it possible to take advantage of the new set of cloud-native technologies such as Docker, when you have applications of mixed architectural styles?


1 2 3 4

Occasional lightweight product and blog updates. Unsubscribe at any time.

© 2009-2018 Rendered Text. All rights reserved. Terms of Service, Privacy policy, Security.