You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potential clashes with untracked files when pulling in on production server after downloading backup
Repo size inflation
1 is a more serious problem. Occurred to me that if the db restore script didn't use Craft's own "backups" directory then it could be gitignored (and potentially backups could be stored as zips rather than raw SQL? In which case .sql files could be ignored and the script could restore the latest zip)
The text was updated successfully, but these errors were encountered:
Two problem with having backups in Git:
1 is a more serious problem. Occurred to me that if the db restore script didn't use Craft's own "backups" directory then it could be gitignored (and potentially backups could be stored as zips rather than raw SQL? In which case .sql files could be ignored and the script could restore the latest zip)
The text was updated successfully, but these errors were encountered: