Make it run, then plan what comes next

Technical: make it run 75 min

What: Make a real 5-service app (Python, Node.js, .NET, Redis, Postgres) start with one flisk up. You need Git, Node.js, Docker and Tilt. If flisk up stops, run npx @flisk-sh/flisk doctor: it names what is missing and how to fix it.

1. Fork the starter. Open flisk-sh/flisk-task-starter and press Fork (top right), then Create fork.

   

   

2. Clone your fork.

   git clone https://github.com/YOUR-LOGIN/flisk-task-starter
   cd flisk-task-starter

3. See the plan. Nothing is written yet. Read what Flisk could not translate: that is your first friction.

   $ npx @flisk-sh/flisk import . --dry-run
   Found 5 service(s) and 0 job(s) in ~/flisk-task-starter
   Read only: docker-compose.yml. Lines below name what was not translated.
   
     .flisk/project.json  [create Flisk project]
     …
     vote  (service, vote/)
       from:      docker-compose.yml [compose]
       build:     vote/ with Dockerfile
       port:      80 (from Compose)
       proxy:     routed through Traefik
       health:    / (assumed)
       depends:   redis
       write:     services/flisk-task-starter/vote/service.json  [create]
     …
   
   Skipped / not fully imported:
     docker-compose.yml [compose]: service "vote" keys not translated: volumes, networks
     docker-compose.yml [compose]: service "result" publishes extra container ports (9229); Flisk routes only 80
     docker-compose.yml [compose]: service "result" keys not translated: entrypoint, volumes, networks
     docker-compose.yml [compose]: service "worker" keys not translated: networks
     docker-compose.yml [compose]: service "redis" keys not translated: volumes, networks
     docker-compose.yml [compose]: service "db" keys not translated: volumes, networks
     docker-compose.yml [compose]: service "seed" has profiles ["seed"]; profiles are not enforced by Flisk
   
   Dry run: nothing written.

4. Write it and start it.

   npx @flisk-sh/flisk import .
   npx @flisk-sh/flisk up

   The first start takes about 90 seconds. Then run npx @flisk-sh/flisk networks for the URLs: the voting page is at /api/vote and the results at /api/result. Open both.
5. Write your README and push. Replace the starter's README.md with yours: how to start it, and a ## What was hard section. Then git add -A && git commit -m "Run with Flisk" && git push.

Deliver Your fork with .flisk/project.json, a service.json per service, the starter's LICENSE and NOTICE, and your README.md.

Product: the next 6 months 45 min

What: Predict what Flisk should ship by six months from now. How: Read, in this order (read only: do not comment or open anything there):

1. docs/ROADMAP.md: what Flisk intends to do over 12 months, and what it will not do.
2. docs/CHANGELOG.md: the Unreleased section and the last few versions. This shows what is being built now. (The GitHub releases page only lists checksums.)
3. The open issues labelled rfc: proposals not decided yet.
4. flisk.sh, the README, and what you learned in Part 1.

Look for the pattern: what keeps being built, and where does it lead in six months? Why: The first hire shapes the roadmap with the founder; we want to see if you understand where Flisk is going and why.

Deliver ROADMAP.md in your fork, in this shape (replace every line in capitals):

## Vision
WHERE FLISK IS GOING, IN ONE OR TWO SENTENCES OF YOUR OWN.

## Next 6 months
| Item | Who it is for | Impact | Confidence | Ease | ICE | Number to watch |
|------|---------------|--------|------------|------|-----|-----------------|
| ITEM | WHO           | 1-10   | 1-10       | 1-10 | I×C×E | METRIC        |
(at least three rows, highest ICE first: quick wins on top)

## Not now
ONE THING FLISK SHOULD NOT BUILD YET, AND WHY.