View categories

Categories

Heroku Architecture
- Compute (Dynos)
  - Dyno Management
  - Dyno Concepts
  - Dyno Behavior
  - Dyno Reference
  - Dyno Troubleshooting
- Stacks (operating system images)
- Networking & DNS
- Platform Policies
- Platform Principles

Command Line

Deployment
- Deploying with Git
- Deploying with Docker
- Deployment Integrations

Continuous Delivery & Integration
- Continuous Integration

Language Support
- Node.js
  - Troubleshooting Node.js Apps
  - Working with Node.js
  - Node.js Behavior in Heroku
- Ruby
  - Rails Support
  - Working with Bundler
  - Working with Ruby
  - Ruby Behavior in Heroku
  - Troubleshooting Ruby Apps
- Python
  - Working with Python
  - Background Jobs in Python
  - Python Behavior in Heroku
  - Working with Django
- Java
  - Java Behavior in Heroku
  - Working with Java
  - Working with Maven
  - Working with Spring Boot
  - Troubleshooting Java Apps
- PHP
  - PHP Behavior in Heroku
  - Working with PHP
- Go
  - Go Dependency Management
- Scala
- Clojure
- .NET

Databases & Data Management
- Heroku Postgres
  - Postgres Basics
  - Postgres Getting Started
  - Postgres Performance
  - Postgres Data Transfer & Preservation
  - Postgres Availability
  - Postgres Special Topics
- Heroku Key-Value Store
- 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)
- Private Spaces
  - Infrastructure Networking
- Compliance

Heroku Enterprise
- 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

Threshold Alerting now in Public Beta

Change effective on 08 July 2016

To help users more easily monitor application health we’ve introduced a new threshold alerting beta feature. This feature allows users to specify tolerances for p95 response time and/or failed request percentage for web dynos, along with sensitivity, the duration an error state must occur (1 minute, 5 minutes or 10 minutes) before an alert is triggered.

Notifications appear in the dashboard and/or via email as specified. More details on this feature are available in Dev Center. Stay tuned for upcoming support for a more refined email distribution and PagerDuty.

New PHP runtimes and extensions All applications now have a config variable limit of 32kb