Heroku Blog
- News
- Last Updated: July 18, 2012
- Harold Giménez
When was the last time you rotated your database credentials? Is it possible that old colleague still has access to your data? Or perhaps they've been accidentally leaked in a screenshot. There are many reasons to rotate your credentials regularly. We now support the ability to easily reset your database credentials, and it is as simple as running the following on your command line: heroku pg:credentials:rotate HEROKU_POSTGRESQL_COLOR –app your-app When you issue the above command, new credentials will be created for your database, and we will update the related config vars on your heroku application. However, on production databases (crane…
- News
- Last Updated: April 11, 2024
- Matthew Manning
Last summer, Heroku became a polyglot platform, with official support for Ruby, Node.js, Clojure, Java, Python, and Scala. Building a platform that works equally well for such a wide variety of programming languages was a unique technical design challenge. siloed products would be a non-scalable design We knew from the outset that maintaining siloed, language-specific products – a Heroku for Ruby, a Heroku for Node.js, a Heroku for Clojure, and so on – wouldn't be scalable over the long-term. Instead, we created Cedar: a single, general-purpose stack with no native support for any language. Adding support for any language is…
- News
- Last Updated: July 16, 2012
- Matthew Soldo
Today, the Heroku Postgres team released into beta the new basic plan, $9 / month version of the dev plan. Accompanying this announcement is the implementation of a 10,000 row limit on the dev plan. This row limit was designed to correspond to the 5mb limit on the existing free shared plan. Please note that these plans are still beta, and Heroku Postgres has not yet announced a migration schedule from the shared plan. However you can start using these plans today. Read more about the new plan, and the mechanics of the row limits on the Heroku Postgres Blog.
- News
- Last Updated: July 16, 2012
- Matthew Soldo
Six weeks ago we launched into beta the Heroku Postgres dev plan, a postgres 9.1 plan that offers many of the features of our production tier service. Over 3,000 of these dev databases are in active use, and it has been operating exceptionally well. When we launched the dev plan, we wrote that the plan would be limited based on rows rather than physical byte size. Today we are implementing a 10,000 row limit for the dev plan. This limit was chosen to correspond to the 5mb limit on the existing, shared database service. Over 98% of the active shared…
- News
- Last Updated: May 06, 2024
- Byron Sebastian
Heroku learned of and resolved a security vulnerability last week. We want to report this to you, describe how we responded to the incident, and reiterate our commitment to constantly improving the security and integrity of your data and source code. On Tuesday, June 26, Jonathan Rudenberg notified us about an issue in our Codon build system. The Codon build system is responsible for receiving application code from Git and preparing it for execution on the Aspen and Cedar stacks. This vulnerability exposed a number of sensitive credentials which could be used to obtain data and source code of customer…
- News
- Last Updated: April 30, 2024
- Keith Rarick
The Heroku Cedar stack went public beta last year with a series of blog posts. Since then, over 80,000 developers have deployed over 4.5 million times, to apps written in dozens of different programming languages and frameworks. Today, over 75 percent of Heroku app development activity is on the Cedar stack. Production apps like Banjo, Rapportive, PageLever, do.com, and Project Zebra run on Cedar; some of these serve hundreds of millions or even billions of requests per month. Cedar features a streamlined HTTP stack allowing for advanced HTTP capabilities, heroku run for execution of arbitrary one-off dynos, Procfile and the…
Subscribe to the full-text feed.