View categories

Categories

Heroku Architecture
- Dynos (app containers)
- Stacks (operating system images)
- Networking & DNS
- Platform Policies
- Platform Principles

Deployment
- Deploying with Git
- Deployment Lifecycle
  - Continuous Integration
- Deployment Integrations

Command Line

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

Monitoring & Metrics
- Logging

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

App Performance

Add-ons
- All Add-ons

Collaboration

Security
- App Security
- Identities & Authentication
- Compliance

Heroku Enterprise
- Private Spaces
- Enterprise Teams
- Heroku Connect (Salesforce sync)
- Single Sign-on (SSO)

Heroku Labs

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

Accounts & Billing

Troubleshooting & Support

Platform API now supports running dynos with custom environment

Change effective on 13 September 2013

The API to run dynos now take env, a hash of custom environment variables to be added to that particular run.

Ruby 2.1.0 preview1 now supported on Heroku Platform API addon services and plans list `slug` ranges renamed to `name`