LaraKube CLI was built to bridge that gap. It allows you to stop being "just a coder" and start being an Infrastructure Architect.

The Power of "Architecture-by-Flag"​

In a traditional setup, adding something like Redis or Meilisearch involves hunting down Docker Compose snippets and manually mapping ports. In LaraKube, it’s a single flag.

larakube new my-app --frankenphp --mysql --redis --meilisearch

With one command, you aren't just creating a Laravel folder; you are scaffolding an industrial-strength infrastructure stack.

Professional Defaults, No Magic​

We don't use "black box" magic. LaraKube generates standard, pure Kustomize YAML manifests. This means that as you grow, you can look inside the .infrastructure folder and learn how professional Kubernetes manifests are structured.

Why It Matters​

When you build with LaraKube, you are building for scale from Day One. You get:

• Automated SSL: Real wildcard certificates for your local .dev.test domains.
• Dedicated Workers: Isolated pods for Horizon and Scheduled tasks.
• Service Isolation: Your database isn't just a process; it's a secured service in your namespace.

Stop managing servers. Start orchestrating masterpieces. 🏛️🏗️

Enter the FrankenPHP Revolution.

What is FrankenPHP?​

FrankenPHP is a modern PHP app server that brings the power of Laravel Octane to the masses. Instead of booting your framework 1,000 times for 1,000 requests, Octane boots it once and keeps it in memory.

Why It’s a Game Changer in LaraKube​

When you use LaraKube CLI with the --frankenphp flag, you aren't just getting a faster web server. You are getting:

1. Persistent Connections: Your database and Redis connections stay open, eliminating the "handshake" overhead on every request.
2. Native Worker Mode: Your app is served by a high-performance C-based Go server that manages PHP workers with incredible efficiency.
3. Automated Live-Watching: In LaraKube, we've integrated chokidar so that when you save a file, the Octane workers restart instantly inside your cluster.

Production-Ready Performance, Locally​

The best part? Because LaraKube uses the same Server Side Up images in your local cluster that you use in production, your performance benchmarks are actually meaningful. You aren't testing on a "fake" local setup; you are testing on your actual infrastructure.

If you haven't tried running your Laravel app in memory yet, now is the time. 🚀🐘⚡️

In a traditional setup, this would be a nightmare. In LaraKube, it’s a non-event. This is the power of Architectural Resilience.

Blueprint Resilience​

LaraKube CLI introduces a unique strategy called Blueprint Resilience. Every time you run a command, your project's architectural DNA is automatically backed up to a secure Kubernetes Secret inside your cluster.

If your local configuration is ever lost, you can simply run:

larakube heal

The CLI will detect the missing local blueprint and offer to restore it directly from the cluster. Your infrastructure is effectively indestructible.

Self-Healing Manifests​

We’ve all had those moments where we manually "tweaked" a YAML file and broke everything. The heal command acts as your personal infrastructure consultant. It surgically regenerates your manifests and patches, ensuring they always follow the latest LaraKube stability standards.

The Peace of Mind​

By treating your infrastructure as a living, self-healing entity, you can:

• Upgrade with Confidence: Apply new LaraKube features to old projects safely.
• Collaborate Without Fear: Ensure every developer on your team is using the exact same, valid manifest structure.
• Sleep Better: Knowing that your cluster has its own "immune system."

Infrastructure doesn't have to be fragile. With LaraKube, it's resilient by design. 🛡️✨

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:

1. Absolute Portability: Your app doesn't care if it's on a Mac, Windows (WSL2), or Linux.
2. Production Parity: You are running the exact same Docker images in development that you will use in production.
3. 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. 🚀