Skip to main content

Our Philosophy

LaraKube is built on a Container-First philosophy. We believe that a developer's host machine should be kept as clean and "factory-original" as possible.

🚀 Zero-Host Dependency​

LaraKube assumes you don't have PHP, Composer, or Node installed on your Mac or Linux machine.

  • Isolated Creation: When you run larakube new, the CLI pulls a specialized installer image to build your app.
  • Isolated Maintenance: Tasks like installing dependencies (composer install, npm install) happen inside ephemeral containers, not on your host.
  • Consistency: By using containers for everything, we guarantee that "it works on my machine" means "it works on everyone's machine."

🔐 Identity & Permissions (UID/GID)​

One of the biggest pain points of mounting local folders into containers on Linux is file ownership (files being created as root).

  • Automatic Mapping: LaraKube automatically detects your host's User ID and Group ID.
  • Transparent Ownership: It maps these IDs into the running Kubernetes pods. Any file generated by Laravel (like logs or compiled views) is owned by you on your host machine, making it easy to edit or delete without sudo.

📦 Service Isolation​

LaraKube strictly separates concerns into dedicated pods:

  • PHP Pod: Handles the Laravel application and Composer tasks.
  • Node Pod: Handles Vite, asset compilation, and Hot Module Replacement (HMR).
  • Service Pods: Databases and queues run in their own hardened environments.

This isolation ensures that a frontend build error never crashes your backend, and vice versa.