Your answers: Python · Docker Compose · 5 or more 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, …)   |
Great fit. Flisk was made for teams like yours.
- ✅ Flisk can create Python parts for you (
flisk resource … --language python), and there is a ready example. - ✅ Your team already uses containers. Flisk writes those setup files for them and keeps them in sync.
- ✅ 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.
- ✅ 5 or more parts is what Flisk is for. Our tests start 100 small test parts at once (test stubs, not a real app).
- ✅ 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 | Python | 18 / 20 |
| How you start it today | Docker Compose | 16 / 20 |
| Pains (we assumed) | Slow onboarding, laptops that differ | 12 / 24 |
| Parts | 5 or more parts | 20 / 20 |
| Team size (we assumed) | 10 developers | 14 / 16 |
| Score | 80% |
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.