Take a stack that already works under `flisk up` to Heroku with that host's own tooling - a Heroku app with config vars, and a Procfile or the container registry. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Heroku. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
Installs into .claude/skills of the current project.
Are you the author of Flisk Deploy Heroku?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-heroku)
---
name: flisk-deploy-heroku
description: Take a stack that already works under `flisk up` to Heroku with that host's own tooling - a Heroku app with config vars, and a Procfile or the container registry. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Heroku. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. Heroku CLI recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Heroku
Flisk is local-only. This skill covers deploying to Heroku.
## Workflow
1. Confirm the stack works locally: `flisk doctor && flisk up <stack>`.
2. Extract the contract from service.json.
3. Create a Heroku app and set config vars.
4. Use a Procfile or container registry for the services.
5. Deploy and verify health endpoints.
## Guardrails
- Do not deploy local generated files.
- Keep production config separate from local service.json.
