Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Can anyone share how they are doing backups and restore of multiple Laravel projects?
In particular, I'm concerned with DB, .env and storage as these are not version controlled.
Preferably it is all done via SSH.
I'm hoping it is easy to setup, verify that it is working correctly and of course, easy to restore too.
For DB, I just dump:
mysqldump -uzzzzzzz -pzzzzzzzz --add-drop-database --databases --routines tjtransactions > "D:\zipfold\mysql_backs\xbacks\tjtransactions.sql"
But I believe Spatie has a routine for this, check theit site, or I know github has packages for this also.
I use spatie backup with the target as S3, on about 20 sites.
However, I probably restored less than a handful in 10 years.
@laracoft My code is a repository that’s on both my computer and GitHub; user-uploaded assets are stored in S3; and my applications are deployed to Heroku, which automatically creates a database back-up daily.
I host all my own sites since I run a home datacenter so I have backups on the application storage, db & file storage on raspberry pi 5s with 2tb nand ssds, also off site backups to my dedicated server on ovh
Well. I have my codebase as repository on Github. DB is supabase and storage is S3. And the server where i have Laravel forge installed has a daily backup.
N.B: The repository is private.
I bundle my db dump, env, and storage into a tar.gz and push it over SSH with a tiny bash script; restoring is just extracting and running migrate. For storage-heavy projects, I clean old junk with tools I already use, and I’ve wiped external disks for cold backups using https://hddformat.com, which made resets painless before reusing drives for off‑server copies.
Please or to participate in this conversation.