Protect me from cleaning up.

[tddewey]

It's possible to delete everything. let's be a bit more careful both in generating and in cleanup. Proposed:

• Only allow the generator to run if the current directory is empty (except for an allowed vvv.json and any file ending in .sql or .sql.gz). This prevents us from running the generator in, for example, www.
• When cleaning up, explicitly target the files that yo created. So if, somehow, it's generated in the wrong folder — or we add new stuff to the generated folder — we only clean up the mess we made.

[lkwdwrd]

Still considering this one... we could go the easy route and call out each of the generated files, but I've had a couple of situations pop up. I downloaded an entire install for testing and stuffed it into htdocs and used bootstrap to finish putting together the rest of the install pieces. It would be nice to have a way to identify pieces of the install to clean even if they would normally be part of the default install. Perhaps this is enough of an edge case to leave it be and have people manually back up files rather than provide a way to save them automatically.

[EHLOVader]

I would really like this also to protect if the repos pulled in haven't been pushed. This would save some trouble in case you haven't sent your changes to the remotes.

An example of how to possible check for this would be below:

git fetch origin
git branch -r --contains HEAD