View categories

Categories

Language Support
- Node.js
- Ruby
  - Working with Bundler
  - Rails Support
- Python
  - Background Jobs in Python
  - Working with Django
- Java
  - Working with Maven
  - Java Database Operations
  - Java Advanced Topics
  - Working with Spring Boot
- PHP
- Go
  - Go Dependency Management
- Scala
- Clojure

Databases & Data Management
- Heroku Postgres
  - Postgres Basics
  - Postgres Getting Started
  - Postgres Performance
  - Postgres Data Transfer & Preservation
  - Postgres Availability
  - Postgres Special Topics
- Heroku Data For Redis
- Apache Kafka on Heroku
- Other Data Stores

Monitoring & Metrics
- Logging

App Performance

Add-ons
- All Add-ons

Collaboration

Security
- App Security
- Identities & Authentication
  - Single Sign-on (SSO)
- Compliance

Heroku Enterprise
- Private Spaces
  - Infrastructure Networking
- Enterprise Accounts
- Enterprise Teams
- Heroku Connect (Salesforce sync)
  - Heroku Connect Administration
  - Heroku Connect Reference
  - Heroku Connect Troubleshooting

Patterns & Best Practices

Extending Heroku
- Platform API
- App Webhooks
- Heroku Labs
- Building Add-ons
  - Add-on Development Tasks
  - Add-on APIs
  - Add-on Guidelines & Requirements
- Building CLI Plugins
- Developing Buildpacks
- Dev Center

Accounts & Billing

Troubleshooting & Support

Integrating with Salesforce

New Python Buildpack release

Change effective on 06 April 2020

The Official Python Buildpack v168 has been released.

This release include bug fixes and documentation updates.

In addition, the legacy method of vendoring GEO libraries has been deprecated. If your app requires these libraries, please switch to the Heroku Geo Buildpack.

For more information about Heroku’s Python support, check out Heroku Python Support.

New logging infrastructure and L14 reporting change Cedar-14 stack End-of-Life window extended to November 2, 2020