Deploy Laravel
FrankenPHP, Vite assets built during the build, a PostgreSQL database and migrations in a job.
Queues and scheduling
Run queued jobs in a background worker, on the database or Redis, and the scheduler beside it.
Object storage
Store uploads in a bucket with Laravel’s
s3 disk, with temporary or public URLs.Caching
Keep the cache and sessions in a Redis or Valkey database.
How the guides fit together
- The deploy guide creates the
storefrontproject withcomposer create-project, deploys it with Ingot, and connects it to a PostgreSQL database namedorders-db. Laravel’s defaults keep sessions, the cache and queued jobs in that database, so the application needs nothing else to run. - Each topic guide starts from that project, adds code and environment variables, and deploys again. The guides don’t depend on each other, so follow them in any order.
- Every guide works with both build strategies. Ingot needs no build configuration. The deploy guide also writes a Dockerfile for full control of the image, and each topic guide says what to change in it, such as a PHP extension Ingot installs on its own.