Menu

Laravel Production Deployment Checklist: 25 Things to Check
📰

Laravel Production Deployment Checklist: 25 Things to Check

DEV Community: laravel·Aqib Javaid·13 days ago
#CUrd1Y1o
#devtolaravel#devto#dev#deploy#cache
Reading 0:00
15s threshold

Most Laravel launch problems are not exotic. They are a missed environment variable, a queue worker that was never started, a debug page left switched on, or a migration that locked a table. This Laravel production deployment checklist is the list I run through before and after a go-live. It works whether you deploy with a managed tool, a container platform or your own server. If you want help doing it, my cloud and DevOps deployment service covers exactly this kind of work.

Use it as a working document: copy it into your repository and tick items off per release.

Before you deploy: environment and configuration#

APP_ENV=production and APP_DEBUG=false . Debug mode can leak stack traces, environment values and queries to anyone who triggers an error.

A unique APP_KEY generated for production and stored outside the repository. Never reuse the development key.

Secrets live in the environment , not in committed files.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.