Announcing A Very Ruby Thanksgiving

We’re very excited that our Heroku colleagues Matz, Nobu and Ko1 will all be visiting from Japan soon to attend RubyConf, and it’s especially serendipitous that it is happening in such close proximity to Thanksgiving. Not only is Thanksgiving one of the few holidays that Japan and the U.S. share, it’s a holiday that brings families together to reflect on what’s been accomplished, and to share insight into the future. We've been waiting for just the right opportunity to organize a small Ruby gathering and Thanksgiving provides the perfect setting.

Read more →

Announcing HTTP Git Beta

Of the many Platform-as-a-Service innovations Heroku has contributed in its seven year existence, perhaps the most iconic is git push heroku master. Today we’re announcing a significant upgrade to Heroku’s Git implementation: Beta support for Git’s HTTP transport.

HTTP Git has some notable advantages over traditional SSH Git. Instead of relying on port 22 (often blocked by firewalls) HTTP Git runs on port 443, the same port used for secure web requests.

Also, HTTP Git uses a simpler authentication model than SSH Git, and is easier to set up. Many new users struggle with the tooling and configuration required to configure git-push over SSH, especially on Windows. HTTP Git uses Heroku API tokens for authentication, and Heroku Toolbelt takes care of setup and configuration so that you’re not prompted for your password on each push. See the Authentication section on Dev Center for details on how auth is managed.

Read more →

Cedar-14 now Generally Available

We’re excited to announce that the Cedar-14 – the new version of the Celedon Cedar stack – is ready for general availability and is now the default stack on Heroku. Cedar-14 is based on the latest Ubuntu LTS Linux version and comes with a modern set of libraries and system dependencies that will stay current and updated for a long time to come.

Since we announced the public beta of Cedar-14 three months ago, we have migrated most of the apps that we run on Heroku to Cedar-14 (yes, a lot of Heroku runs on the Heroku platform) and thousands of users have also moved apps or created new Cedar-14 apps. We have worked with these early adopters and with buildpack maintainers to weed out bugs and problems. Cedar-14 is now stable and ready for production apps.

Read on to learn how to migrate apps to Cedar-14 and for details on future stack updates on Heroku.

Read more →

Introducing Heroku CX Patterns: Building Customer Experiences on Heroku with Salesforce Services

A quick glance at most any phone shows the importance and urgency – for businesses of all kinds – of creating mobile customer apps. Our everyday activities – finding a ride, ordering a meal or turning on a light are increasingly mobile experiences.

But delivering a great omnichannel experience to customers requires more than just the work of the application developer. The larger organization is involved in following up with prospects, fielding service inquiries, and sending relevant marketing messages. Orchestrating this tapestry of touchpoints often requires developers to integrate with systems used by non-developers, including sales, service, marketing and community management systems.

Read more →

Behind the Heroku Platform: How We Create Non-events for Customers

As an SRE (Service Reliability Engineer) at Heroku, one of the things I’m exposed to is how much work happens behind the scenes in order to create what we call “non-events” for you, our users. A non-event is turning something that would typically create work for an application hosted on traditional infrastructure into something that the user won’t even notice. This is something we put a lot of energy into because we believe in letting our users run apps instead of managing infrastructure. We make this investment because we know that for every hour you spend managing infrastructure, that’s an hour less spent on building or maintaining your application. We know that you need to be able to iterate quickly in order to have a competitive advantage and you’ll have a more difficult time doing that if you’re also managing infrastructure.

Two examples of these non-events from recent weeks are the “Shellshock” security flaw and Amazon having to reboot a large number of instances due to a security vulnerability in their hypervisor. This post is about what happened behind the scenes at Heroku to shield our users.

Read more →

Browse the blog archives or subscribe to the full-text feed.

Visit the Engineering Blog