ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide whether to deploy a pre‑built Docker image or use Scalingo’s buildpacks by comparing build time, runtime flexibility, cold‑start latency, and storage usage, then follow the concrete steps to deploy and verify.
Background Scalingo keeps a per‑application buildpack cache to speed up subsequent builds. The cache persists until the user clears it via the CLI or dashboard. Current documentation does not state that the cache is automatically refreshed when a dependency manifest (e.g., Gemfile, package.json, Pipfile) is modified. Unresolved Decision When a dependency ver
Node.js Buildpack Component When deploying applications to Scalingo, the buildpack detection process relies on the runtime version specified in the application configuration. If the requested Node.js version falls outside the currently supported matrix provided by the platform, the build phase is rejected. While explicit runtime pinning or buildpack override
docker
scalingo
nodejs