Skip to main content

Install SkillFlaw

This page is the shared deployment entrypoint for choosing between the SkillFlaw Python backend and SkillFlaw TypeScript backend installation tracks.

Choose your deployment track​

Python backend deployment​

Choose the Python deployment guide when your target runtime is based on:

  • docker/docker-compose-py.yml
  • docker/backend/Dockerfile
  • make init / make init_db
  • make backend / make frontend

Go to: Install SkillFlaw for deployment - Python

TypeScript backend deployment​

Choose the TypeScript deployment guide when your target runtime is based on:

  • docker/docker-compose-ts.yml
  • ghcr.io/cwinux/skillflaw_backend_ts:latest
  • make ts_install_backend / make ts_init_db
  • make ts_backend
  • make ts_backend_verify

Go to: Install SkillFlaw for deployment - TypeScript

Quick comparison​

TrackCompose fileBackend service/imageDatabase entrypointDefault frontendDefault backend health
Pythondocker/docker-compose-py.ymlbackend_py / local Python backend imagemake init_db or Python compose bootstraphttp://localhost:3001http://localhost:7860/health
TypeScriptdocker/docker-compose-ts.ymlbackend_ts / ghcr.io/cwinux/skillflaw_backend_ts:latestmake ts_init_db or TypeScript compose bootstraphttp://localhost:3003http://localhost:7861/health

Docker installation​

Use Docker when you want a packaged local or deployment-style product stack.

Source installation​

Use source installation when you want repository-controlled deployment, debugging, or runtime validation.

Shared deployment notes​

  • the frontend remains shared across both backend runtimes
  • the docs site remains shared across both backend runtimes
  • the default docs image is still ghcr.io/cwinux/skillflaw_docs:latest
  • the default frontend image is still ghcr.io/cwinux/skillflaw_frontend:latest