As you know last Sunday we had a large maintenance window during which DeployBot was unavailable. That was the inconvenient part that we're sorry about. However, there was also an exciting part to that maintenance about which I want to tell you today.
Creating an automated deployment service like DeployBot is a big responsibility. Our users depend on us during their most important deployments and their day to day workflows. When things break, businesses and teams suffer. We don't take this responsibility lightly, so we are constantly working on the ways we can improve the stability and performance of DeployBot.
Unfortunately in many cases this work goes on under the hood and is not directly visible to our customers. In this post, I'm going to summarize all the good things that happened to DeployBot's internals over the last year.
Caching CSS, JS, and images for a long period of time is one of the most important things you can do to create a fast website loading. It’s relatively easy to configure on most web servers, but comes with a downside — you’ll need to invalidate cached files whenever they change.
Today we're glad to announce a new integration with Honeybadger. Honeybadger is a great service that provides exception, uptime and performance monitoring for your applications. Now with this new DeployBot integration, you'll be able to track your deployments in Honeybadger and see how they affected the state of your app.
Have you ever thought of DeployBot as just another co-worker of yours? You know, that spherical robot guy who helps you continuously deliver all these awesome updates straight to your customers. If you haven’t, it’s likely because you’re not using ChatOps capabilities that we’ve built into it.
In this new guide, we’ll explain what ChatOps is, and how you can employ DeployBot to implement ChatOps. You’ll learn how to send your deployment notifications to Slack and use chat commands to trigger manual deployments.