kmx.io/ex_ovh

diff --git a/docs/getting_started_advanced.md b/docs/getting_started_advanced.md
deleted file mode 100644
index f166cbb..0000000
--- a/docs/getting_started_advanced.md
+++ /dev/null
@@ -1,67 +0,0 @@
-# Getting Started
-
-## Installation 
-
-- Add `:ex_ovh` to the dependencies.
-
-```elixir
-defp deps() do
-  [{:ex_ovh, "~> 0.2"}]
-end
-```
-
-## Configuration
-
-*Note:* The configuration assumes that the environment variables such as `MY_APP_OVH_CLIENT_CLIENT_ID` are already created.
-
-- Create an OVH account at [OVH](https://www.ovh.com/us/)
-
-- Create an API application at the [OVH API page](https://eu.api.ovh.com/createApp/). Follow the
-  steps outlined by OVH there. Alternatively, there is a [mix task](https://github.com/stephenmoloney/ex_ovh/blob/master/docs/mix_task_advanced.md) which can help
-  generate the OVH application.
-  
-- Add the configuration settings for the OVH application to your project `config.exs`.
-
-```elixir
-config :my_app, MyApp.OvhClient,
-   ovh: [
-     application_key: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_KEY"),
-     application_secret: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_SECRET"),
-     consumer_key: System.get_env("MY_APP_OVH_CLIENT_CONSUMER_KEY"),
-     endpoint: "ovh-eu",
-     api_version: "1.0"
-   ],
-   httpoison: [ # optional
-     connect_timeout: 20000,
-     receive_timeout: 100000
-   ]
-```
-
-- Start the `ExOvh` application.
-
-```elixir
-def application do
- [applications: [:ex_ovh]]
-end
-```
-
-- Add the client to your project.
-
-```elixir
-defmodule MyApp.OvhClient do
-  @moduledoc :false
-  use ExOvh.Client, otp_app: :my_app, client: __MODULE__
-end
-```
-
-- Add the client as a supervisor directly to the supervision tree of your application.
-
-```elixir
-def start(_type, _args) do
-  import Supervisor.Spec, warn: false
-  spec1 = [supervisor(MyApp.Endpoint, [])]
-  spec2 = [supervisor(MyApp.OvhClient, [])]
-  opts = [strategy: :one_for_one, name: MyApp.Supervisor]
-  Supervisor.start_link(spec1 ++ spec2, opts)
-end
-```
\ No newline at end of file
diff --git a/docs/getting_started_basic.md b/docs/getting_started_basic.md
deleted file mode 100644
index afe00b8..0000000
--- a/docs/getting_started_basic.md
+++ /dev/null
@@ -1,102 +0,0 @@
-# Getting Started (Basic)
-
-The basic installation is intended for use cases where only a single client is required
-on a given server.
-
-#### Installation 
-
-- Add `:ex_ovh` to the dependencies.
-
-```elixir
-defp deps() do
-  [{:ex_ovh, "~> 0.2"}]
-end
-```
-
-#### `OVH` Configuration
-
-- Create an OVH account at [OVH](https://www.ovh.com/us/)
-
-- Create an API application at the [OVH API page](https://eu.api.ovh.com/createApp/). Follow the
-  steps outlined by OVH there.
-
-- Add the configuration settings for the OVH application to your project `config.exs`. The following
-environment variables should be set:
-
-    - `EX_OVH_APPLICATION_KEY`
-    - `EX_OVH_APPLICATION_SECRET`
-    - `EX_OVH_CONSUMER_KEY`
-
-- Set them by adding them to the `.env` file. It's best not to share `.env` so run
-echo '.env' >> .gitignore` for the git repository to ensure it doesn't get added to source control.
-
-The `.env` file will be similar to as follows:
-```
-#!/usr/bin/env bash
-
-# updated on 16.2.2017
-export MY_APP_OVH_CLIENT_APPLICATION_KEY="<application_key>"
-export MY_APP_OVH_CLIENT_APPLICATION_SECRET="<application_secret>"
-export MY_APP_OVH_CLIENT_CONSUMER_KEY="<application_consumer_key>"
-```
-
-- If all of the above seems like too much work, then there is a mix task to help generate the application, see
-[basic mix task](https://github.com/stephenmoloney/ex_ovh/blob/master/docs/mix_task_basic.md) or
-[advanced mix task](https://github.com/stephenmoloney/ex_ovh/blob/master/docs/mix_task_advanced.md)
-
-
-
-#### Some useful requests in the `OVH console` to see applications
-
-- `GET /me/api/application` -- returns a list of application ids.
-- `GET /me/api/application/{applicationId}` -- returns json with application key.
-
-
-#### Creating the appropriate `config.exs` file.
-
-```elixir
-config :ex_ovh,
-  ovh: [
-    application_key: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_KEY"),
-    application_secret: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_SECRET"),
-    consumer_key: System.get_env("MY_APP_OVH_CLIENT_CONSUMER_KEY")
-  ]
-```
-
-- Start the `ExOvh` application.
-
-```elixir
-def application do
- [applications: [:ex_ovh]]
-end
-```
-
-- Add the client to your project.
-
-```elixir
-defmodule ExOvh do
-  @moduledoc :false
-  use ExOvh.Client, otp_app: :my_app, client: __MODULE__
-end
-```
-
-- Add the `ExOvh` client to the supervision tree of your application.
-
-```elixir
-def start(_type, _args) do
-  import Supervisor.Spec, warn: false
-  spec1 = [supervisor(MyApp.Endpoint, [])]
-  spec2 = [supervisor(ExOvh, [])]
-  opts = [strategy: :one_for_one, name: MyApp.Supervisor]
-  Supervisor.start_link(spec1 ++ spec2, opts)
-end
-```
-
-- Now you are read to use the api, open up an `iex` console and give it a try.
-
-```
-iex -S mix
-```
-ExOvh.
-```
-
diff --git a/docs/mix_task.md b/docs/mix_task.md
index e69de29..d9ede9f 100644
--- a/docs/mix_task.md
+++ b/docs/mix_task.md
@@ -0,0 +1,128 @@
+# Mix Task
+
+#### Generate ExOvh Config
+
+The ovh mix task makes requests to the OVH API on the user's behalf to generate an OVH application.
+
+- The mix task:
+
+  1. Creates an application on the user's behalf by sending http requests using the user's username and password credentials.
+  2. Gets a consumer key and validation url.
+  3. Validates the validation url on the user's behalf by sending http requests using the user's username and password credentials.
+  4. Adds the application key, application secret and associated consumer key to the environment configuration.
+  
+The environment variables generated by the task are automatically save to a `.env` file. It is best to ensure that this file is outside
+version control.
+
+
+#### Example 1
+
+
+**Shell input:**
+
+```shell
+mix ovh \
+--login=<username-ovh> \
+--password=<password> \
+--appname='ex_ovh'
+```
+
+- `login`: username/nic_handle for logging into OVH services. *Note*: must include `-ovh` at the end of the string.
+- `password`: password for logging into OVH services.
+- `appname`: this should correspond to the `otp_app` name in the elixir application. It also doubles as the application name 
+for the application in the OVH servers.
+- `redirecturi`: defaults to `""` when absent.
+- `endpoint`: defaults to `"ovh-eu"` wen absent.
+- `accessrules`: defaults to `get-[/*]::put-[/*]::post-[/*]::delete-[/*]` when absent giving the application all
+  full priveleges. One may consider fine-tuning the accessrules, see advanced example below.
+- `appdescription`: defaults to `appname` if absent
+- `clientname`:" This is the elixir client name. defaults to `ExOvh` when the appname is exactly equal to `ex_ovh`, otherwise defaults to `OvhClient`.
+
+
+**Shell Output:**
+
+```elixir
+config :ex_ovh,
+  ovh: [
+    application_key: System.get_env("EX_OVH_APPLICATION_KEY"),
+    application_secret: System.get_env("EX_OVH_APPLICATION_SECRET"),
+    consumer_key: System.get_env("EX_OVH_CONSUMER_KEY"),
+    endpoint: "ovh-eu",
+    api_version: "1.0"
+  ]
+```
+
+Terms explained:
+
+- `EX_OVH_APPLICATION_KEY`: The system environment variable name for the application key.
+- `EX_OVH_APPLICATION_SECRET`: The system environment variable name for the application secret.
+- `EX_OVH_CONSUMER_KEY`: The system environment variable name for the consumer key.
+
+
+#### Example 2
+
+**Shell Input:**
+
+```shell
+mix ovh \
+--login=<username-ovh> \
+--password=<password> \
+--appdescription='Ovh Application for my app' \
+--endpoint='ovh-eu' \
+--apiversion='1.0' \
+--redirecturi='http://localhost:4000/' \
+--accessrules='get-[/*]::put-[/me,/me/*,/cdn/webstorage,/cdn/webstorage/*]::post-[/me,/cdn/webstorage,/cdn/webstorage/*]::delete-[/cdn/webstorage,/cdn/webstorage/*]' \
+--appname='my_app' \
+--clientname='OvhClient'
+```
+
+- `login`: username/nic_handle for logging into OVH services. *Note*: must include `-ovh` at the end of the string.
+- `password`: password for logging into OVH services.
+- `appname`: this should correspond to the `otp_app` name in the elixir application. It also doubles as the application name
+for the application in the OVH servers.
+- `clientname`:" This is the elixir client name. defaults to `ExOvh` when the appname is exactly equal to `ex_ovh`, otherwise defaults to `OvhClient`. `clientname` corresponds to the name of the client. So for example, if appname is `'my_app'` and clientname is
+  `'Client'` then the config file will be `config :my_app, MyApp.Client`. Also, the client in application code can be referred
+  to as `MyApp.Client.function_name`.
+- `appdescription`: A description for the application saved to OVH.
+- `endpoint`: OVH endpoint to be used. May vary depending on the OVH service. See `ExOvh.Defaults`.
+- `apiversion`: version of the api to use. Only one version available currently.
+- `redirecturi`: redirect url for oauth authentication. Should be https.
+- `accessrules`: restrictions can be added to the access rules. In this example, `get` requests to all endpoints are allowed,
+  `put` and `post` requests to `/me` and `/cdn` and `delete` requests are forbidden.
+
+
+**Shell Output:**
+
+
+```elixir
+config :my_app, MyApp.OvhClient,
+    ovh: [
+      application_key: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_KEY"),
+      application_secret: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_SECRET"),
+      consumer_key: System.get_env("MY_APP_OVH_CLIENT_CONSUMER_KEY"),
+      endpoint: "ovh-eu",
+      api_version: "1.0"
+    ]
+```
+
+
+Terms explained:
+
+- `MY_APP_OVH_CLIENT_APPLICATION_KEY`: The system environment variable name for the application key.
+- `MY_APP_OVH_CLIENT_APPLICATION_SECRET`: The system environment variable name for the application secret.
+- `MY_APP_OVH_CLIENT_CONSUMER_KEY`: The system environment variable name for the consumer key.
+
+
+#### Add the settings to the environment
+
+- Copy the configuration outputted by the commandline to `config.exs`.
+
+- The enviroment variables are saved to a file called `.env` automatically by the mix task.
+**Do not add the `.env` file to version control.** It would be prudent to add `.env` to the `.gitignore` file.
+Add the variables to the system environment by running the command or some other commands as appropriate
+to the deployment method.
+
+
+```shell
+source .env
+```
\ No newline at end of file
diff --git a/docs/mix_task_advanced.md b/docs/mix_task_advanced.md
deleted file mode 100644
index 84ed27f..0000000
--- a/docs/mix_task_advanced.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# Mix Task (Advanced)
-
-## Generate client config
-
-The ovh mix task makes requests to the OVH API on the user's behalf to generate an OVH application.
-
-- The mix task:
-
-  1. Creates an application on the user's behalf by sending http requests using the user's username and password credentials.
-  2. Gets a consumer key and validation url.
-  3. Validates the validation url on the user's behalf by sending http requests using the user's username and password credentials.
-  4. Adds the application key, application secret and associated consumer key to the environment configuration.
-
-The environment variables generated by the task are automatically save to a `.env` file. It is best to ensure that this file is outside
-version control.
-
-
-**Shell Input:**
-
-```shell
-mix ovh \
---login=<username-ovh> \
---password=<password> \
---appdescription='Ovh Application for my app' \
---endpoint='ovh-eu' \
---apiversion='1.0' \
---redirecturi='http://localhost:4000/' \
---accessrules='get-[/*]::put-[/me,/me/*,/cdn/webstorage,/cdn/webstorage/*]::post-[/me,/cdn/webstorage,/cdn/webstorage/*]::delete-[/cdn/webstorage,/cdn/webstorage/*]' \
---appname='my_app' \
---clientname='OvhClient'
-```
-
-- `login`: username/nic_handle for logging into OVH services. *Note*: must include `-ovh` at the end of the string.
-- `password`: password for logging into OVH services.
-- `appname`: this should correspond to the `otp_app` name in the elixir application. It also doubles as the application name 
-for the application in the OVH servers.
-- `clientname`:" This is the elixir client name. defaults to `ExOvh` when the appname is exactly equal to `ex_ovh`, otherwise defaults to `OvhClient`. `clientname` corresponds to the name of the client. So for example, if appname is `'my_app'` and clientname is
-  `'Client'` then the config file will be `config :my_app, MyApp.Client`. Also, the client in application code can be referred
-  to as `MyApp.Client.function_name`.
-- `appdescription`: A description for the application saved to OVH.
-- `endpoint`: OVH endpoint to be used. May vary depending on the OVH service. See `ExOvh.Defaults`.
-- `apiversion`: version of the api to use. Only one version available currently.
-- `redirecturi`: redirect url for oauth authentication. Should be https.
-- `accessrules`: restrictions can be added to the access rules. In this example, `get` requests to all endpoints are allowed,
-  `put` and `post` requests to `/me` and `/cdn` and `delete` requests are forbidden.
-
-  
-**Shell Output:**
-
-
-```elixir
-config :my_app, MyApp.OvhClient,
-    ovh: [
-      application_key: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_KEY"),
-      application_secret: System.get_env("MY_APP_OVH_CLIENT_APPLICATION_SECRET"),
-      consumer_key: System.get_env("MY_APP_OVH_CLIENT_CONSUMER_KEY"),
-      endpoint: "ovh-eu",
-      api_version: "1.0"
-    ]
-```
-
-
-Terms explained:
-
-- `MY_APP_OVH_CLIENT_APPLICATION_KEY`: The system environment variable name for the application key.
-- `MY_APP_OVH_CLIENT_APPLICATION_SECRET`: The system environment variable name for the application secret.
-- `MY_APP_OVH_CLIENT_CONSUMER_KEY`: The system environment variable name for the consumer key.
-
-
-- Copy the configuration outputted by the commandline to `config.exs`.
-
-
-- The enviroment variables are saved to a file called `.env` automatically by the mix task.
-**Do not add the `.env` file to version control.** Add the variables to the system environment
-by running the command or some other commands as appropriate to the deployment method.
-
-```shell
-source .env
-```
\ No newline at end of file
diff --git a/docs/mix_task_basic.md b/docs/mix_task_basic.md
deleted file mode 100644
index 9bdc9e7..0000000
--- a/docs/mix_task_basic.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Mix Task (Basic)
-
-## Generate ExOvh Config
-
-The ovh mix task makes requests to the OVH API on the user's behalf to generate an OVH application.
-
-- The mix task:
-
-  1. Creates an application on the user's behalf by sending http requests using the user's username and password credentials.
-  2. Gets a consumer key and validation url.
-  3. Validates the validation url on the user's behalf by sending http requests using the user's username and password credentials.
-  4. Adds the application key, application secret and associated consumer key to the environment configuration.
-  
-The environment variables generated by the task are automatically save to a `.env` file. It is best to ensure that this file is outside
-version control.
-
-**Shell input:**
-
-```shell
-mix ovh \
---login=<username-ovh> \
---password=<password> \
---appname='ex_ovh'
-```
-
-- `login`: username/nic_handle for logging into OVH services. *Note*: must include `-ovh` at the end of the string.
-- `password`: password for logging into OVH services.
-- `appname`: this should correspond to the `otp_app` name in the elixir application. It also doubles as the application name 
-for the application in the OVH servers.
-- `redirecturi`: defaults to `""` when absent.
-- `endpoint`: defaults to `"ovh-eu"` wen absent.
-- `accessrules`: defaults to `get-[/*]::put-[/*]::post-[/*]::delete-[/*]` when absent giving the application all
-  full priveleges. One may consider fine-tuning the accessrules, see advanced example below.
-- `appdescription`: defaults to `appname` if absent
-- `clientname`:" This is the elixir client name. defaults to `ExOvh` when the appname is exactly equal to `ex_ovh`, otherwise defaults to `OvhClient`.
-
-
-**Shell Output:**
-
-```elixir
-config :ex_ovh,
-  ovh: [
-    application_key: System.get_env("EX_OVH_APPLICATION_KEY"),
-    application_secret: System.get_env("EX_OVH_APPLICATION_SECRET"),
-    consumer_key: System.get_env("EX_OVH_CONSUMER_KEY"),
-    endpoint: "ovh-eu",
-    api_version: "1.0"
-  ]
-```
-
-Terms explained:
-
-- `EX_OVH_APPLICATION_KEY`: The system environment variable name for the application key.
-- `EX_OVH_APPLICATION_SECRET`: The system environment variable name for the application secret.
-- `EX_OVH_CONSUMER_KEY`: The system environment variable name for the consumer key.
-
-
-- Copy the configuration outputted by the commandline to `config.exs`.
-
-
-- The enviroment variables are saved to a file called `.env` automatically by the mix task.
-**Do not add the `.env` file to version control.** Add the variables to the system environment
-by running the command or some other commands as appropriate to the deployment method.
-
-
-```shell
-source .env
-```
\ No newline at end of file