<commit_before>Varying Vagrant Vagrants
========================

A series of varying Vagrant setups from [@jeremyfelt](http://github.com/jeremyfelt)
* with awesome assists from fellow 10upers [@carldanley](http://github.com/carldanley), [@ericmann](http://github.com/ericmann), [@lkwdwrd](http://github.com/lkwdwrd) and [@TheLastCicada](http://github.com/TheLastCicada)

### So this is Vagrant...
I'm still learning this [Vagrant](http://vagrantup.com) stuff, so take anything I say or put into this repo right now with a huge grain of salt.

But, I think this actually works. Actually, after a couple months, it works really well.

### How?
Start with any operating system, then...

1. First install [VirtualBox 4.2.8](https://www.virtualbox.org/wiki/Downloads). This is the magic that helps the magic behind Vagrant run. I will have you know that I had to uninstall my previous version of VirtualBox and install with the latest before I was able to get Vagrant to work. Results will vary.
1. Download and install [Vagrant 1.1.0](http://downloads.vagrantup.com/tags/v1.1.0), you will now have access to the `vagrant` command via whatever terminal you use.
1. Clone this repo onto your machine in a directory where you want your environment to be stored:
    * `git clone git://github.com/jeremyfelt/varying-vagrant-vagrants.git vagrant-local-dev`
1. Change into this new directory created with the repo:
    * `cd vagrant-local-dev`
1. Start Vagrant:
	* `vagrant up` - *omg magic happens*
	* Once this build process is initiated, a ~280MB virtual machine will download and startup as a sandboxed local environment.
1. Add a record to your hosts file so that we can access the default WordPress installation:
	* `192.168.50.4  local.wordpress.dev`
1. Visit `http://local.wordpress.dev/` in your browser and install WordPress

Fancy, yeah?

### Now What?
Now that you're up and running with a default configuration, start poking around and modifying things.

1. Access the server with `vagrant ssh` from your `vagrant-local-dev` directory. You can do pretty much anything you would do with a standard Ubuntu installation on a full server.
1. Destroy the box and start from scratch with `vagrant destroy`
    * The initial ~280MB file will be cached on your machine, though on the next `vagrant up` it will need to go through the provisioning process, which requires access to the Internet for various apt source packages.
1. Power off the box with `vagrant halt` or suspend it with `vagrant suspend`. If you suspend it, you can bring it back quickly with `vagrant resume`, if you halt it, you can bring it back with `vagrant up`.<commit_msg>Bump VirtualBox version to 4.2.10<commit_after>Varying Vagrant Vagrants
========================

A series of varying Vagrant setups from [@jeremyfelt](http://github.com/jeremyfelt)
* with awesome assists from fellow 10upers [@carldanley](http://github.com/carldanley), [@ericmann](http://github.com/ericmann), [@lkwdwrd](http://github.com/lkwdwrd) and [@TheLastCicada](http://github.com/TheLastCicada)

### So this is Vagrant...
I'm still learning this [Vagrant](http://vagrantup.com) stuff, so take anything I say or put into this repo right now with a huge grain of salt.

But, I think this actually works. Actually, after a couple months, it works really well.

### How?
Start with any operating system, then...

1. First install [VirtualBox 4.2.10](https://www.virtualbox.org/wiki/Downloads). This is the magic that helps the magic behind Vagrant run. I will have you know that I had to uninstall my previous version of VirtualBox and install with the latest before I was able to get Vagrant to work. Results will vary.
1. Download and install [Vagrant 1.1.0](http://downloads.vagrantup.com/tags/v1.1.0), you will now have access to the `vagrant` command via whatever terminal you use.
1. Clone this repo onto your machine in a directory where you want your environment to be stored:
    * `git clone git://github.com/jeremyfelt/varying-vagrant-vagrants.git vagrant-local-dev`
1. Change into this new directory created with the repo:
    * `cd vagrant-local-dev`
1. Start Vagrant:
	* `vagrant up` - *omg magic happens*
	* Once this build process is initiated, a ~280MB virtual machine will download and startup as a sandboxed local environment.
1. Add a record to your hosts file so that we can access the default WordPress installation:
	* `192.168.50.4  local.wordpress.dev`
1. Visit `http://local.wordpress.dev/` in your browser and install WordPress

Fancy, yeah?

### Now What?
Now that you're up and running with a default configuration, start poking around and modifying things.

1. Access the server with `vagrant ssh` from your `vagrant-local-dev` directory. You can do pretty much anything you would do with a standard Ubuntu installation on a full server.
1. Destroy the box and start from scratch with `vagrant destroy`
    * The initial ~280MB file will be cached on your machine, though on the next `vagrant up` it will need to go through the provisioning process, which requires access to the Internet for various apt source packages.
1. Power off the box with `vagrant halt` or suspend it with `vagrant suspend`. If you suspend it, you can bring it back quickly with `vagrant resume`, if you halt it, you can bring it back with `vagrant up`.
{'fraction_non_alphanumeric': 0.09240052800301717, 'fraction_numerical': 0.014520082971902697, 'mean_word_length': 4.3093093093093096, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 8, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1606254', 'n_tokens_mistral': 1574, 'n_tokens_neox': 1506, 'n_words': 731}