This is the official Heroku buildpack for Python applications. It implements the standard buildpack lifecycle (detect, compile, release, report) to install a Python runtime and manage dependencies using pip, pipenv, poetry, or uv. It handles Django collectstatic, NLTK corpora downloads, user-supplied hooks (pre/post compile), and Heroku CI. The codebase is a collection of modular shell scripts with a consistent library pattern, extensive integration tests via Hatchet/RSpec, and support for multiple Heroku stacks. It is actively maintained, with Dependabot for dependency updates and CI workflows for every commit. The architecture is straightforward: each lifecycle phase is a standalone script that sources reusable libraries from lib/. While the core logic is specific to Heroku's platform, the library functions (e.g., caching, version resolution, build data reporting) demonstrate good shell scripting practices and could be adapted for other build systems.
This repository is a Heroku buildpack designed to enable Puppeteer (a Node.js library for controlling headless Chrome/Chromium) to run on Heroku dynos. It installs the necessary system-level dependencies (shared libraries, fonts) required for Chromium to function in Heroku's Linux container environment. The buildpack consists of two scripts: bin/detect, which simply returns 'Puppeteer' to signal applicability, and bin/compile, which handles the core logic of detecting the Heroku stack, installing appropriate APT packages via apt-get with caching, setting up environment variables (LD_LIBRARY_PATH, etc.), and rewriting pkg-config files to ensure the installed libraries are discoverable by the application. The buildpack demonstrates solid engineering practices for Heroku buildpacks, including stack-aware dependency caching to speed up subsequent builds, proper environment variable propagation for downstream buildpacks, and clean separation of concerns. While the functionality is niche and the code is not exceptionally innovative, it is well-structured, maintainable, and solves a specific problem effectively. The repository has been updated to support recent Heroku stacks (heroku-22, heroku-24, heroku-26), indicating ongoing maintenance.