flisk/demosGitHub

Personal Flisk demo

@yourhandle's Flisk stack

✓
Repo ready
  • ✓ flisk resource ×2
  • ✓ flisk config verify
Open the repo on GitHub

Why this stack

saleor integration

This stack uses placeholder .env keys for saleor. A real saleor integration is built by hand, the way we did for Thor Commerce. We've logged a request for it.

Run it

npm install -g @flisk-sh/flisk
git clone -b demo/yourhandle-store-1dd9bf https://github.com/flisk-sh/demos.git store-demo
cd store-demo
cp .env.example .env
flisk doctor
flisk up
Or scaffold it yourself
npm install -g @flisk-sh/flisk
flisk doctor
flisk project --yes
flisk resource web --type frontend --stack store --framework vue --yes
flisk resource api --type backend --stack store --yes
flisk up store
flisk status

.env.example

Copy to .env and fill in your keys. It never leaves your machine.

SALEOR_API_URL=
SALEOR_API_KEY=

Your service.json files

One service.json each. Postgres comes from "prisma" and Traefik routing is built in, so neither needs its own file.

webfrontendvue app
// services/store/web/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "web",
  "appType": "frontend",
  "stack": "store",
  "port": 3000,
  "framework": "vue",
  "dependsOn": [
    "api"
  ]
}
apibackendbackend-for-frontend: the only service holding saleor keys
// services/store/api/service.json
{
  "$schema": "https://flisk.sh/schema.service.json",
  "schemaVersion": 1,
  "appName": "api",
  "appType": "backend",
  "stack": "store",
  "port": 4000,
  "healthCheckPath": "/health"
}

Want one for a friend?

Ask @grok on X with their handle and what they build.

Make one for a friend