Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
C0D4669025yIf it's for data, automate a backup process or snapshots on a scheduled task and.. I'm assuming mysql based on profile... just run mysql_dumps and upload them to an external storage.
I wouldn't put a DB into version control unless it's only structural information/ stored procedures and configurational data that would be used in the event you needed to create a new DB and somehow loose the snapshots. -
rytzpekt2705yThere is a DB designed for this use case. Quite handy IMHO.
https://github.com/attic-labs/noms -
@C0D4
One by one
Have you been using any services to
1. automate a backup process -
2 .take snapshots on a scheduled task - -
C0D4669025y@sandeepbalan not since moving everything to AWS a few years ago which we have private S3 buckets for.
But before that I had VMWare run daily snapshots of the VMs and I just wrote a php cronjob that exported the database with exec(mysql_dump) on a daily basis, zip it up, and send it to another server, ah the good ol' days.
Related Rants
Is there any version control system for database..
Ofcourse we can keep sql file for mysql db along with our code. Other than that .....
"I mean i want my db backup,
I do not want to do it myself every time,
It should work like pulling code"
question
backup
thoughts
versioncontrol
db
code