Fixes #1883: Drop 'official-ish' support for using Drupal VM for prod.

Author: geerlingguy

.gitignore

@@ -20,7 +20,5 @@ Vagrantfile.local
 /config.yml
 /docker-compose.yml
 /drupal.make.yml
-/examples/prod/inventory
-/examples/prod/bootstrap/vars.yml
 /scripts/
 /drupal/

docs/other/production.md

@@ -1,7 +1,11 @@
-Drupal VM supports deploying Drupal VM to a production environment. The security of your servers is _your_ responsibility.
+Drupal VM can be made to manage a production environment. The security of your servers is _your_ responsibility, and **such usage should be considered experimental and unsupported**.
 
 (See companion blog post to this documentation: [Soup to Nuts: Using Drupal VM to build local and prod](https://www.jeffgeerling.com/blog/2017/soup-nuts-using-drupal-vm-build-local-and-prod).)
 
+If you want to try managing a production environment (or other non-local environments) with Drupal VM, please see the following suggestions for making these servers more secure and easier to manage.
+
+> Note: As of Drupal VM 5.0.0, the example production configuration files are no longer included with Drupal VM. You would need to download [Drupal VM 4.9.1](https://github.com/geerlingguy/drupal-vm/releases/tag/4.9.1) and copy the `examples/prod` directory into your Drupal VM codebase to make the example commands work with a newer version of Drupal VM.
+
 ## Production specific overrides.
 
 Drupal VM supports loading configuration files depending on the environment variable `DRUPALVM_ENV` and using this feature you can have different configurations between development and production environments.
@@ -57,7 +61,7 @@ And if you need to override one of the secrets stored in that file, you can do s
 
 ## Example: Drupal VM on DigitalOcean
 
-The [`examples/prod` directory](https://github.com/geerlingguy/drupal-vm/tree/master/examples/prod) contains an example production configuration for Drupal VM which can be used to deploy Drupal VM to a production environment on a cloud provider like DigitalOcean, Linode, or AWS.
+The [`examples/prod` directory](https://github.com/geerlingguy/drupal-vm/tree/4.9.1/examples/prod) contains an example production configuration for Drupal VM which can be used to deploy Drupal VM to a production environment on a cloud provider like DigitalOcean, Linode, or AWS.
 
 This guide contains instructions for how you can build a Drupal environment with Drupal VM on DigitalOcean.
 
@@ -70,7 +74,7 @@ Make sure you have an SSH key you can use to connect to your DigitalOcean drople
 Once you are logged into DigitalOcean and have added your SSH key, click the 'Create Droplet' button on your Droplets page. For the Droplet, choose the following options:
 
   - **Image**: Choose `Ubuntu 16.04.x x64`
-  - **Size**: 1 GB / 1 CPU (currently $10/month; you can choose a higher plan if needed)
+  - **Size**: 1 GB / 1 CPU (currently $5/month; you can choose a higher plan if needed)
   - **Region**: Choose whatever region is geographically nearest to you and your site visitors
   - **Settings**: (Nothing here affects how Drupal VM works, choose what you'd like)
   - **Add SSH Keys**: Select the SSH key you added to your account earlier.
@@ -88,9 +92,9 @@ Your DigitalOcean Droplet is booted and ready to have Drupal VM installed on it.
 
 ### Customize `config.yml` for production
 
-Copy [`examples/prod/prod.config.yml`](https://github.com/geerlingguy/drupal-vm/blob/master/examples/prod/prod.config.yml) to `config.yml`, and by looking at `default.config.yml` add any other overrides you'd like. Whatever variables you have set in `config.yml` will override the defaults set by `default.config.yml`.
+Copy [`examples/prod/prod.config.yml`](https://github.com/geerlingguy/drupal-vm/blob/4.9.1/examples/prod/prod.config.yml) to `config.yml`, and by looking at `default.config.yml` add any other overrides you'd like. Whatever variables you have set in `config.yml` will override the defaults set by `default.config.yml`.
 
-The changes outlined in the [example `prod.config.yml`](https://github.com/geerlingguy/drupal-vm/blob/master/examples/prod/prod.config.yml) disable development-environment tools (like Pimp My Log and Adminer) and add extra security hardening configuration (via the `extra_security_enabled` variable).
+The changes outlined in the [example `prod.config.yml`](https://github.com/geerlingguy/drupal-vm/blob/4.9.1/examples/prod/prod.config.yml) disable development-environment tools (like Pimp My Log and Adminer) and add extra security hardening configuration (via the `extra_security_enabled` variable).
 
 You now have Drupal VM configured for production by default. This is the recommended and safest way, so that you can't accidentally provision a production server with development tools. If desired you can also use the [environment variable `DRUPALVM_ENV`](#production-specific-overrides) to load an additional `<ENV>.config.yml` with production specific overrides. In most cases this is not needed though.