<commit_before>Vagrant-Chef-LEMP
=================

A starting point for PHP web site projects.  A basic project with a Vagrant configuration with Chef
provisioning for setting up a LEMP stack (Linux, nginx, MySQL, PHP).

This project uses Vagrant to encapsulate the technology stack for a PHP web application in a virtual
machine, for development. It uses Chef to automatically configure virtual machine instances, so that
both development and production virtual machine instances will be the product of source code, not
manual labor. This keeps the technology stack consistent and predictable, and it keeps all
developers on the exact same technology stack.  The beauty of Vagrant is that you run your code
using a stable technology stack running on a VM that is the product of source code, but you can edit
your code using your favorite native tools in your host OS.  You get the best of both worlds.

## Usage

Embed this project as a folder in your PHP project.  You might want to consider embedding it as a
Git submodule.  This project will share the ```..``` folder with the Vagrant VM as its
```/vagrant``` folder.  That's the document root for the nginx server, so the root of your PHP
project will be the root of the web server in the Vagrant VM.  You'll be able to access it at
```http://localhost:7777```.

## Provisioning

This project uses Chef to provision the Vagrant VM.  Specifically,
[chef-solo](https://docs.chef.io/chef_solo.html).  It would be simple to swap out this technology
stack configuration for another one that uses Docker or something else to configure the Vagrant VM.

## Development
<commit_msg>A plugin, not a project to fork.<commit_after>Vagrant-Chef-LEMP
=================

A pluggable PHP technology stack for developing web site projects.  A basic project with a Vagrant
configuration with Chef provisioning for setting up a LEMP stack (Linux, nginx, MySQL, PHP).

## Purpose

This project uses Vagrant to encapsulate the technology stack for a PHP web application in a virtual
machine, for development. It uses Chef to automatically configure virtual machine instances, so that
both development and production virtual machine instances will be the product of source code, not
manual labor. This keeps the technology stack consistent and predictable, and it keeps all
developers on the exact same technology stack.  The beauty of Vagrant is that you run your code
using a stable technology stack running on a VM that is the product of source code, but you can edit
your code using your favorite native tools in your host OS.  You get the best of both worlds.

## Usage

Embed this project as a folder in your PHP project.  You might want to consider embedding it as a
Git submodule.  This project will share the ```..``` folder with the Vagrant VM as its
```/vagrant``` folder.  That's the document root for the nginx server, so the root of your PHP
project will be the root of the web server in the Vagrant VM.  You'll be able to access it at
```http://localhost:7777```.

## Provisioning

This project uses Chef to provision the Vagrant VM.  Specifically,
[chef-solo](https://docs.chef.io/chef_solo.html).  It would be simple to swap out this technology
stack configuration for another one that uses Docker or something else to configure the Vagrant VM.

## Development

{'fraction_non_alphanumeric': 0.057971014492753624, 'fraction_numerical': 0.0024154589371980675, 'mean_word_length': 4.352180936995153, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5021052', 'n_tokens_mistral': 864, 'n_tokens_neox': 820, 'n_words': 515}