Practical guides for securing and monitoring Laravel and PHP apps on your own server.
· 3 min read
Most breaches of PHP apps come through a vulnerable package, not your own code. How to run composer audit, read the output, wire it into CI, and handle packages that cannot be updated.
· 4 min read
Everything to verify before and after you put a Laravel app on a server you manage yourself: web server, configuration, permissions, HTTPS, queues, backups and monitoring.
· 1 min read
A dead queue worker looks like a healthy site: pages load, but emails and jobs never run. How to keep the worker alive with systemd, restart it on deploy, and get alerted when it stops.
· 4 min read
Five HTTP response headers close off whole classes of browser attacks. The exact nginx config for each, the add_header inheritance trap, and how to roll out a CSP without breaking your app.
· 4 min read
An exposed .env file hands attackers your database password, APP_KEY and API keys. Here is how to test for it in ten seconds, fix it in nginx or Apache, and clean up if it was open.
· 4 min read
Leaving APP_DEBUG on turns every error into a page of internals for anyone who triggers it. What it exposes, how to check your app, and why config caching trips people up.
The free scan looks for exposed files, missing security headers and SSL problems. No signup required.
Run the free scan