Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[PR] Only mount shared DB drive if already mounting #322
This shifts the default behavior for VVV to non-persisting
This addresses the pain that is #287 and moves to a model that
We'll probably want to think of ways we can avoid data loss by
referenced this pull request
Apr 4, 2014
I just did a fresh
DB data is no longer persistent, so if
I'm going to go in the direction of providing default DB backups only if a custom script does not exist. If a custom script is added, then we'll assume it is handling DB backups on its own. If nothing else, the defaults can be copied to this new custom file if they need to run in addition. This way we aren't stomping on or defining any workflows too strictly.
I'll do a better overall writeup later. For now, I'm going through the process of converting another machine and I'm taking notes. This is moving a powered off virtual machine to a non persistent DB. If you're starting in a destroyed state, the second set won't be necessary.
At this point, MySQL is horribly broken because we surprised it by taking the directory away.
Heads up, the above doesn't work that great, but it is close. The conversion process sucks. I ended up destroying so I could start over. I'll revisit at some point soon.