The Zero-Host Philosophy: Why Your Machine Deserves Better
As Laravel developers, we’ve all been there: brew upgrade accidentally breaks your local PHP version, or a Node.js update causes your Vite build to explode. You spend three hours fixing your environment instead of building your masterpiece.
At LaraKube CLI, we believe your host machine should be kept as "factory-original" as possible. This is the Zero-Host Philosophy.
The Problem with Native Runtimes
When you install PHP, Nginx, and Node directly on your macOS or Windows machine, you are building on a foundation of "it works on my machine." But the moment you deploy to a server, everything changes. The paths are different, the permissions are different, and the performance characteristics are different.
The LaraKube Solution
LaraKube CLI is now distributed as a standalone binary. It doesn't need PHP or Node on your machine to work. Instead, it orchestrates everything inside Kubernetes containers.
By moving your entire development stack into a local k3s cluster, you get:
- Absolute Portability: Your app doesn't care if it's on a Mac, Windows (WSL2), or Linux.
- Production Parity: You are running the exact same Docker images in development that you will use in production.
- A Clean Machine: No more messy PATH variables or conflicting global npm packages.
Getting Started
The shift is simple. Instead of running php artisan, you use LaraKube to launch your cluster:
larakube up
Your machine stays clean, your cluster stays stable, and your focus stays on the code. Welcome to the future of Laravel development. 🚀