Your answers: Ruby or PHP · They just run the code, no Docker · 2–4 parts. Click a tab to change one; the score updates.
1. What is the app written in?      |
2. How do developers start the app on their laptop today?         |
3. How many parts does the app have? (website, API, background jobs, …)   |
Could fit. Flisk will help; read the notes below first.
- 🟡 Flisk runs Ruby and PHP apps, but cannot create new parts in them for you yet. Developers keep their own setup file.
- ✅ No Docker needed: Flisk starts each part with the command your team already uses.
- ✅ New developers start with two commands (
flisk doctor,flisk up) instead of a long setup guide. Not yet timed with real new hires. - ✅ Every laptop gets the same base setup, so "it works on my machine" happens less.
- 🟡 A few parts already benefit; Flisk shines from about 5.
- ✅ The score assumes a team of 10 developers. It is simple math on your answers, not measured savings.
How the score adds up
| Your answer | Points | |
|---|---|---|
| Language | Ruby or PHP | 12 / 20 |
| How you start it today | They just run the code, no Docker | 16 / 20 |
| Pains (we assumed) | Slow onboarding, laptops that differ | 12 / 24 |
| Parts | 2–4 parts | 12 / 20 |
| Team size (we assumed) | 10 developers | 14 / 16 |
| Score | 66% |
Same math as flisk.sh/fit. Two things have no tabs here, so we assumed them (marked "we assumed"); change them on the website. The score never says "great fit" when a reason above says otherwise.
Next: install Flisk and pick how to start.