Preview environments for Laravel + Vue

Yes — Inertia is the default assumption. Your Laravel routes return Inertia responses, Vite builds the Vue pages, and the whole thing serves from one origin, so there are no CORS hoops and shared props just work. Inertia SSR is supported too: add the SSR build/serve commands and we run the Node SSR process alongside PHP.

On every deploy we run your install and build steps in a container — typically `npm ci` (or pnpm/yarn) then `npm run build`, which runs Vite and emits the hashed assets Laravel’s Vite helper references. The compiled manifest ships with the environment, so the preview serves production-built assets, not a dev server.

Each environment gets its own isolated MySQL or PostgreSQL database. We run `php artisan migrate` and your seeders on first boot, so the preview opens on realistic data instead of an empty schema. Tear-down drops the database with the environment — no shared staging to clobber.

Your project’s env template is rendered per environment: APP_URL is set to the generated HTTPS URL, a fresh APP_KEY is generated, and database/Redis credentials are injected to point at that environment’s own services. Secrets you define on the project are merged in.

Yes. The same image runs a `queue:work` worker and the scheduler, so jobs, broadcasts and scheduled tasks behave like production. Redis is provisioned for cache, sessions and queues by default.

As long as you need it. Each environment runs on its own auto-expiring lease you can renew or pin to a PR; idle ones tear down on their own so you never pay for an environment you forgot about.