ShippedLaravel hosting
on Shipped.
Your Laravel product includes more than its web routes. Ship the application, connect its data, and run the background work that keeps it useful.
Give the web app its production home
Deploy Laravel with its PHP runtime, dependencies, and production server configuration. Keep the public directory as the web entry point and provide private configuration through secrets. Shipped handles the public address and HTTPS while your routes, middleware, controllers, and templates remain part of the application.
Run queues and schedules alongside it
Laravel jobs often send messages, process uploads, or perform work that should outlast a request. Run queue workers separately from the web service and schedule recurring tasks deliberately. Connect the appropriate queue backend and database so job state and application records remain available across process replacement.
Preserve the things customers create
Keep uploaded files in persistent object storage through the storage integration your app uses. Manage database migrations as part of a checked release, and test changes in staging before production. App rollback restores code; data recovery and reversing a schema change are separate operations with their own consequences.
A little more detail
Questions about Laravel?
Can Laravel queue workers deploy separately?
Yes. Use a worker service with the appropriate command and connections. It can share the application source while having its own capacity and process lifecycle.
Does deployment replace the Laravel application key?
Keep the application key in stable secret configuration. Changing it can affect encrypted data and sessions, so it should not be regenerated as a routine side effect of releasing code.
From your workspace to the web