Ignore entire wp-content directory in wordpress-default
Ignore data directories created by mysql
Merge remote-tracking branch 'carldanley/master' into vvvv-0.2
Specify database name during database import

Mysql needs a database name to be specified if it isn't already so in the SQL file being imported
Refactor handling of initial database setup

Our naming convention was a little weird before and various scripts for mysql were kind of hidden all over. This does a few things...

* Establishes an init.sql file that creates our default WordPress database and an external user to be used by the local machine for non SSH tunnel connections to mysql. This init.sql file will be where any SQL specific to this vagrant repo will be stored.

* Establishes the concept of an init-custom.sql file that will be used on individual setups to control the databases and users created during a vagrant up. This file must be created by the user, but a sample is included in init-custom.sql.sample

* Ditches create-dbs.sql.sample and default-dbs.sql in favor of this new naming convention
* Alters .gitignore in favor of the new naming convention
* Reorgs the order of things in provision.sh to account for the new naming convention
Additional readme for database/data directory
Add commenting to import-sql.sh
Clarify readme for mysqldump files
Cheap check for database before importing

Look for an existing database data directory before trying to import the mysqldump file. This is pretty cheap and may not work as a long term solution, but we'll see.

Addresses Issue #9
Do a true check on existing tables before importing

Rather than looking for a directory, which I could see causing issues in a few places, we use SHOW DATABASES LIKE from the command line to see if the current database already exists.
Improved check for existing database before import

Now this is pretty boss.

Check for tables on each database before attempting to import.
* If a database does not exist, an error is thrown that we catch and add more info to
* If a database does exist, but has tables, we skip it because we more than likely imported already
* If a database does exist, but has no tables, we do the import from database/backups

Sweeeet.
Refresh README to match latest changes
Updated gitignore with comments
Tabs to spaces in bash script
Add clarification to the config.vm.customize option
Create the external database user with a stored procedure

Using a stored procedure allows us to check if the external database user exists before we attempt to create it. This in turn avoids a red error from coming up during the `vagrant up` process.
Refactor Vagrantfile to 1.1.x format

While Vagrant 1.1.x is back compatible with a 1.0.x Vagrantfile, we should be moving along as quickly as possible.
* Introduces the use of the new Vagrant.configure() to indicate which version of the commands we are using.
* Keeps only one 1.0.x command around, though this is more Virtualbox specific, so may be moved to the 1.1.x area shortly
* Uses the correct 1.1.x commands for sync_folder, private_network, etc..
Remove stored procedure due to wth

I didn't think this through the right way. We don't need a stored procedure, we just need a command that doesn't error out.

By using GRANT PRIVILEGES without the CREATE USER command, we ensure that privileges are assigned whether the user already exists or not. If it doesn't, it will automatically be created for us with no error.
Rename config/mysql to config/mysql-config

Our other sub config directories are named {service}-config, this should be too.
s/create-dbs/init-custom/ in existin watchr script