This is my first time here. I recently joined as a system admin at a company and my recent assignment is to make friendlier dev environments for our devs. Until now our devs connect to our remote box, copy the production code, do a restore of the production database, and correct apache vhost settings and then begin development. Most of the development happens via putty and its extremely tedious.
Quite recently I learnt about Vagrant and was amazed by it. So I quickly set up a simple LAMP stack that our devs can use. However, my biggest complication at this point is how to set up a prod db like mysql environment. Our database is around 7GB in size and it doesnt make sense to download it and then run it in your vagrant VM.
I'm sure that this is common problem lots of sysadmins have dealt with in the past. How do I set up a prod-like dev DB since Vagrant without transferring over that massive data dump.
Best Answer
Our developers use a smaller data set than one that's in production. All of the tables are the same, but the data is not a copy of the live data set. This will vary depending on your needs, but for us this is a great way to work.