Heroku Blog
- Ecosystem
- Last Updated: April 28, 2017
- Arif Gursel
Need to quickly catch up on this past quarter's announcements? Here are the top three topics to tune in on: The new add-ons canary service will attempt to provision and deprovision your add-on service on an app named 'addons-canary'. These daily tests will help us proactively detect any failed provisioning attempts and ensure customers can provision all add-on services. This effort will also help us identify issues earlier and notify you of provisioning issues. Heroku Shield, a set of services included in Heroku Enterprise, is generally available and offers customers additional compliance features needed for building high-compliance applications. Heroku Shield…
Your Heroku applications run on top of a curated stack, containing the operating system and other components needed at runtime. We maintain the stack – updating the OS, the libraries, and ensuring that known security issues are resolved, so that you can focus on writing code. Today we're announcing the general availability of Heroku-16, our curated stack based on Ubuntu 16.04 LTS. In addition to a new base operating system, Heroku-16 is updated with the latest libraries. If you’re a Ruby or Python developer, Heroku-16 includes 15% more development headers at build time, making it easier to compile native packages…
- News
- Last Updated: April 30, 2024
- Ike DeLorenzo
How we built Heroku CI: our product intuition checked against what the market wants (we surveyed ~1000 developers to figure out the latter, and the results were surprising) Two approaches to building any product are often in tension: designing from inspiration, and designing from information. On the pure inspiration side, you just build the product you dream of, and trust that it will be so awesome and useful, that it will succeed in the market. On the pure information side, you build exactly what the market is asking for, as best you can tell (think: surveys, top customer feature requests,…
- Engineering
- Last Updated: March 30, 2017
- Lex Neva
Back on August 11, 2016, Heroku experienced increased routing latency in the EU region of the common runtime. While the official follow-up report describes what happened and what we've done to avoid this in the future, we found the root cause to be puzzling enough to require a deep dive into Linux networking. The following is a write-up by SRE member Lex Neva (what's SRE?) and routing engineer Fred Hebert (now Heroku alumni) of an interesting Linux networking "gotcha" they discovered while working on incident 930. The Incident Our monitoring systems paged us about a rise in latency levels across…
- News
- Last Updated: March 28, 2017
- Richard Schneeman
This post is going to help save you money if you're running a Rails server. It starts like this: you write an app. Let's say you're building the next hyper-targeted blogging platform for medium length posts. When you login, you see a paginated list of all of the articles you've written. You have a Post model and maybe for to do tags, you have a Tag model, and for comments, you have a Comment model. You write your view so that it renders the posts: <% @posts.each do |post| %> <%= link_to(post, post.title) %> <%= teaser_for(post) %> <%= "#{post.comments.count} comments"…
- News
- Last Updated: March 21, 2017
- Brett Goulder
We are happy to announce the general availability of Automated Certificate Management (ACM) for all paid Heroku dynos. With ACM, the cumbersome and costly process of provisioning and managing SSL certificates is replaced with a simple experience that is free for all paid Dynos on Heroku’s Common Runtime. Creating secure web applications has never been more important, and with ACM and the Let’s Encrypt project, never easier. ACM handles all aspects of SSL/TLS certificates for custom domains; you no longer have to purchase certificates, or worry about their expiration or renewal. ACM builds directly on our recent release of Heroku…
Subscribe to the full-text feed.