Laravel in production,the whole of it.
A Laravel app in production means PHP, a database, a cache, queues and a scheduler. All five are placed as blocks on the canvas and deployed from your Git repository, without YAML.
Between the local project and production, everything remains to be built.
On a developer’s laptop, Laravel fits in one command. In production it needs a tuned PHP server, a backed-up database, Redis for cache and sessions, workers for the queues and a cron for the scheduler. It is that full architecture, not just the code, that the canvas describes and the platform operates.
The typical Laravel architecture, block by block.
The application
Your Git repository, built and served. Domains, TLS and environment variables set inside the block.
The database
Managed PostgreSQL or MySQL, automatic backups. Credentials are injected into the application.
Redis
Cache, sessions and queues on a dedicated block, sized independently of the application.
The workers
Your queues run on their own resources, scaled with queue depth.
The scheduler
The Laravel cron runs as a scheduled task, with its own logs.
Storage
Files and media on S3-compatible object storage, at the same European provider.
From push to release.
What people ask about Laravel.
They run automatically before traffic switches to the new version. If a migration fails, the deploy stops and the live version is untouched.
Send us your bill.We will tell you what we see in it.
A line-by-line costed estimate within 48 hours, with no commitment.