Tech
flisk.sh is one service.json, then the laptop starts
flisk.sh is a CLI. You describe each service in one service.json . flisk up writes the local wiring and starts that part of the product on your machine.
Docker runs the containers. Tilt live-updates them as you code. Flisk writes the files those two consume: Dockerfiles, Traefik routes, env files, and the Tiltfile. You do not maintain a Compose file for this. You do not boot Kubernetes to change a button. It is not a deploy tool. Production stays on Helm, or on whatever you already ship w...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to