Take a stack that already works under `flisk up` to Cloudflare with that host's own tooling - Cloudflare Pages or Workers, for a Flisk frontend or a compatible service. 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 Cloudflare. 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 Cloudflare?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-cloudflare)
---
name: flisk-deploy-cloudflare
description: Take a stack that already works under `flisk up` to Cloudflare with that host's own tooling - Cloudflare Pages or Workers, for a Flisk frontend or a compatible service. 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 Cloudflare. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. Wrangler CLI recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Cloudflare
Flisk is local-only. This skill covers deploying compatible parts to Cloudflare.
## Workflow
1. Confirm the frontend works locally with `flisk up`.
2. Identify the frontend service (Vite/React/Vue).
3. Use Cloudflare Pages for static/Vite builds or Workers for edge functions.
4. Set environment variables in the Cloudflare dashboard.
5. Deploy with Wrangler or the Git integration and verify.
## Guardrails
- Best for frontends and edge. Full multi-service Docker stacks stay local or go elsewhere.
- Keep the local service.json as the source of truth.
