More obvious naming

The naming was taken from the library we consumed, rather than a
sensible naming for users checking out the mu-cache for the first time.
This new mu-cache handles naming much better.

Author: madnificent

config/config.exs

@@ -20,7 +20,7 @@ end
 # if you want to provide default values for your application for
 # 3rd-party users, it should be done in your "mix.exs" file.
 
-config :use_plug_proxy,
+config :mu_cache,
   log_cache_keys: CH.system_boolean("LOG_CACHE_KEYS"),
   log_clear_keys: CH.system_boolean("LOG_CLEAR_KEYS")
 

lib/use_plug_proxy.ex renamed to lib/mu_cache_plug.ex

@@ -1,6 +1,6 @@
 alias Cache.Registry, as: Cache
 
-defmodule UsePlugProxy do
+defmodule MuCachePlug do
   @moduledoc """
   Router for receiving cache requests.
   """
@@ -49,7 +49,7 @@ defmodule UsePlugProxy do
   end
 
   defp maybe_log_clear_keys(clear_keys) do
-    if Application.get_env(:use_plug_proxy, :log_clear_keys) do
+    if Application.get_env(:mu_cache, :log_clear_keys) do
       # credo:disable-for-next-line Credo.Check.Warning.IoInspect
       IO.inspect(clear_keys, label: "Clear keys")
     end
@@ -58,7 +58,7 @@ defmodule UsePlugProxy do
   end
 
   defp maybe_log_cache_keys(cache_keys) do
-    if Application.get_env(:use_plug_proxy, :log_cache_keys) do
+    if Application.get_env(:mu_cache, :log_cache_keys) do
       # credo:disable-for-next-line Credo.Check.Warning.IoInspect
       IO.inspect(cache_keys, label: "Cache keys")
     end

lib/mu_elixir_cache.ex

@@ -11,7 +11,7 @@ defmodule MuElixirCache do
       {Cache.Registry, %{}},
       {Plug.Cowboy,
        scheme: :http,
-       plug: UsePlugProxy,
+       plug: MuCachePlug,
        options: [
          port: 80,
          protocol_options: [max_header_value_length: 409_600_000, max_keepalive: 1000]

mix.exs

@@ -3,7 +3,7 @@ defmodule UsePlugProxy.Mixfile do
 
   def project do
     [
-      app: :use_plug_proxy,
+      app: :mu_cache,
       version: "2.0.2",
       elixir: "~> 1.5",
       build_embedded: Mix.env() == :prod,