Engineering

Our Laravel + Vue deployment checklist for fintech UIs

January 22, 20268 min read

Developer workstation and code — blog cover

This is the internal checklist we give partners before go-live. It assumes Nginx or similar, PHP-FPM, and a separate build step for the Vue storefront or admin.

Separate APP_KEY per environment; rotate on staff churn.
Cache config and routes in prod; never commit .env.
Serve Nuxt/Vite assets with immutable cache headers where safe.
Health endpoints for queue workers and scheduler heartbeat.

If you’re shipping TradifyLabs-derived code, align API base URLs with your reverse proxy and enable structured logs — grep-friendly JSON beats screenshots in Slack.

Comments

Thoughts and questions on this article. Sign in to post a comment or reply — guests can read the thread only.

Join the discussion

4 comments

Sam T.5d ago
Any gotchas mixing Nuxt SSR behind the same Nginx host as the Laravel API?
- TradifyLabs4d ago
  Keep `/api` on Laravel and `/` on the Node/Nuxt upstream; avoid double gzip and align trusted proxy headers.
Morgan K.6d ago
Should `php artisan config:cache` run in CI or only on the server after deploy?
- TradifyLabs5d ago
  On the server after env is correct — cached config bakes in env at cache time, so CI-only can bite you.
Riley P.1w ago
Health checks for queue workers — single `/health` or separate for redis + horizon?
Devon W.1w ago
We forgot immutable cache headers on Vite assets once and had a fun afternoon. Worth calling out in the checklist PDF.
- Sam T.1w ago
  Same here — hashed filenames + `Cache-Control: immutable` saved us after that.