Update readme's to guide to the right ansible hosts file

Author: Georgi

README.md

@@ -88,11 +88,11 @@ _Before running this script, you need to create a ops/hosts file first.  See the
 This script will:
  - Build release Webpack bundles
  - Package the .NET Core application in Release mode (dotnet publish)
- - Run the ops/deploy.yml Ansible playbook to deploy this app to hosts in /ops/hosts inventory file.
+ - Run the ops/deploy.yml Ansible playbook to deploy this app to hosts in /ops/config.yml inventory file.
 
  This does the following:
   - Copies the build assets to the remote host(s)
-  - Updates the `appsettings.json` file with PostgreSQL credentials specified in ops/hosts file and the app URL (needed for JWT tokens)
+  - Updates the `appsettings.json` file with PostgreSQL credentials specified in ops/group_vars/all file and the app URL (needed for JWT tokens)
   - Restarts the app so that changes will be picked up
 
 ## Development Email Delivery

ops/README.md

@@ -4,14 +4,14 @@ This folder contains [Ansible](https://www.ansible.com/) assets responsible for
 
 1. Procure access to Ubuntu 16.04 (Xenial) or Ubuntu 18.04 (Bionic) host which will be used to host this application.  [AWS](aws.amazon.com) or [Digital Ocean](https://m.do.co/c/974ef9a471c1) are good options.
 2. Setup DNS records to point to these host(s).
-3. Create `hosts` file in this directory, using `hosts.example` as a pattern.
+3. Create `config.yml` file in this directory, using `config.yml.example` as a pattern.
 
 ## Usage
 
 From the root of this respository, run one of the following commands:
-- `npm run provision:prod`: This will provision all production hosts specified in hosts file.
-- `npm run deploy:prod`: This will deploy the app to all production hosts specified in hosts file.
+- `npm run provision:prod`: This will provision all production hosts specified in config.yml file.
+- `npm run deploy:prod`: This will deploy the app to all production hosts specified in config.yml file.
 
 ## Notes
  - The deploy.yml and provision.yml playbooks were written against and tested on Ubuntu 16.
- - The [Ansible Best Practices](http://docs.ansible.com/ansible/playbooks_best_practices.html) document demonstrates using /groups_vars/... for application environment variables (i.e. production / staging) and /group_vars/all for global variables.  However, we are using inventory group variables, all contained within the inventory file (hosts) to define environment and global variables.  Because of this, all the variables are in a single location and easily managed.
+ - The [Ansible Best Practices](http://docs.ansible.com/ansible/playbooks_best_practices.html) document demonstrates using /groups_vars/... for application environment variables (i.e. production / staging) and /group_vars/all for global variables.  However, we are using inventory group variables, all contained within the inventory file (config.yml) to define environment and global variables.  Because of this, all the variables are in a single location and easily managed.