Running Parse on Heroku

Three months ago we announced that Parse would be opening their Cloud Code product so that their customers would be able to deploy their mobile backends to Heroku. This allowed Parse customers to use a full Node.js environment with Cloud Code. With Parse’s recent announcement, we’re taking that one step further, by allowing you to deploy your own Parse API server to Heroku.

What this means for developers is that you will now be able to run all of your Parse services on Heroku, taking advantage of Heroku’s scalable platform as well as Heroku features like Pipelines, Review Apps, and GitHub Sync. Beyond that, because the Parse Server is now open source, you will also be able to extend and expand the Parse core functionality with no limitations.

Read more →

How Lean Poker Teaches Continuous Deployment on Heroku: An Interview with Creator Rafael Ördög

In 2013, Rafael Ördög put poker and code together, the result: Lean Poker, a competitive coding event that teaches continuous deployment and lean startup methodologies. Rafael is based in Budapest, Hungary.

What's Lean Poker?

Lean Poker is a coding workshop that is designed to teach people how to practice continuous deployment and lean startup methodologies. Companies can sponsor a free public event or hold an internal, team-building event for their own employees.

Read more →

Heroku Private Spaces Now Generally Available

Today Heroku is announcing that Heroku Private Spaces is generally available. Introduced in beta in September, Private Spaces is a new Heroku runtime designed from the ground up to meet the trust and control requirements of the most demanding applications. This new architecture enables Private Spaces to deliver the best of both worlds: the easy and powerful Heroku developer experience, combined with the network and trust controls historically only available in on-premise, behind-the-firewall deployments. Made available as part of Heroku Enterprise, Private Spaces makes cloud-based PaaS ready for the most critical enterprise applications.

Read more →

SSO for Heroku Now Generally Available

Today we’re pleased to announce that SSO for Heroku is generally available for Heroku Enterprise customers.

SSO for Heroku supports single sign-on for SAML 2.0 compliant identity providers (IdPs), making it easier for Heroku Enterprise customers to manage identity across various systems. It also simplifies set-up for system administrators, allowing them to focus on managing authentication.

Both cloud and on-premise identity providers are supported by SSO for Heroku. As of today, a number of popular commercial IdPs ship with built-in support for SSO for Heroku, including Salesforce Identity, Okta, PingOne and PingFederate. SSO for Heroku is also fully compatible with identity services from Microsoft Active Directory.

Salesforce SSO for Heroku Set up

For more detailed information, see our previous post, and our Heroku Dev Center docs for IdP administrators, or their end-users. IdP vendors interested in integrating with SSO for Heroku are invited to contact us. Finally, we welcome any feedback from end users on additional IdPs you’d like to see supported.

Upgrading to Rails 5 Beta - The Hard Way

Rails 5 has been brewing for more than a year. To take advantage of new features, and stay on the supported path, you'll need to upgrade. In this post, we'll look at the upgrade process for a production Rails app, The codebase is open source so you can follow along. Special thanks to Prathamesh for his help with this blog post.

How Stable is the Beta?

In Rails a beta means the API is not yet stable, and features will come and go. A Release Candidate (RC) means no new features; the API is considered stable, and RCs will continue to be released until all reported regressions are resolved.

Should you run your production app on the beta? There is value in getting a beta working on a branch and being ready when the RC or upcoming release is available. Lots of companies run Beta and RC releases of Rails in production, but it's not for the faint of heart. You'll need to be pretty confident in your app, make sure your test suite is up to par, and that manual quality control (QC) checks are thorough. It's always a relief to find and fix bugs before they arrive in production. Please report regressions and bugs you encounter -- the faster we uncover and report them, the faster these bugs get fixed, and the more stable Rails becomes. Remember, no one else is going to find and report the regressions in your codebase unless you do it.

Read more →

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