Analysis updated 2026-08-14 · repo last pushed 2024-12-13
Deploy Python apps that use Poetry for dependency management in cloud environments.
Automate Python package installation during cloud deployment pipelines.
Maintain Plotly-specific buildpack customizations while syncing with the upstream community project.
| plotly/paketo-buildpacks_poetry-install | 0verflowme/cloudflared | 0verflowme/pulumi-vultr | |
|---|---|---|---|
| Language | Go | Go | Go |
| Last pushed | 2024-12-13 | 2024-10-19 | 2022-12-26 |
| Maintenance | Stale | Stale | Dormant |
| Setup difficulty | hard | moderate | hard |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | ops devops | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a Paketo/Cloud Foundry buildpack environment and familiarity with Go buildpack internals to modify or integrate.
This repository, maintained by Plotly, is a customized version of an open-source tool called a "buildpack." Buildpacks handle the behind-the-scenes work of preparing applications to run in cloud environments. Specifically, this one deals with installing Poetry, a popular dependency management tool for Python projects. It helps ensure that when someone deploys a Python app, the right packages get installed automatically. The repository itself is a fork, meaning it's a copy of an existing open-source project with Plotly-specific modifications layered on top. It keeps track of the original project in a separate branch called main-upstream, so Plotly can pull in updates from the community whenever needed. The actual custom changes live on the main branch, and release-specific versions are branched off when it's time to freeze code for deployment. The people who'd interact with this repo are primarily Plotly's own engineers and release managers who work on deploying Python applications. If a Plotly team relies on Poetry to manage their Python dependencies, this buildpack would be part of the pipeline that makes their app deployment-ready. It's the kind of infrastructure piece that most end users never see, but it matters for anyone responsible for getting Python services running reliably in the cloud. The README doesn't go into detail about what specific custom changes Plotly has made or what the buildpack does beyond the basics described above. It focuses almost entirely on the branching and release workflow, how updates flow from the upstream community project into Plotly's version, and how changes get prepared for each release. The project is written in Go, which is typical for buildpacks, but you wouldn't need to touch that code unless you were modifying the buildpack itself.
A Plotly-customized buildpack that automatically installs Poetry (a Python dependency manager) when deploying Python apps to the cloud, based on an open-source upstream project.
Mainly Go. The stack also includes Go.
Stale — no commits in 1-2 years (last push 2024-12-13).
No license information is provided in the explanation, this is a fork of an open-source project but specific licensing details are not mentioned.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.