Merge ~mthaddon/charm-k8s-content-cache/+git/charm-k8s-content-cache:deploy-from-charmstore into charm-k8s-content-cache:master

[Tom Haddon]

Update README for deploying from charmstore

Update README for deploying from charmstore

[🤖 Canonical IS Merge Bot (canonical-is-mergebot)]

This merge proposal is being monitored by mergebot. Change the status to Approved to merge.

[Gareth Woolridge (moon127)]

LGTM

review: Approve

[🤖 Canonical IS Merge Bot (canonical-is-mergebot)]

Change successfully merged at revision bf52300397d7494f6164499478a472e14066e94c

diff --git a/README.md b/README.md
index b1002ff..ddca31c 100644
--- a/README.md
+++ b/README.md
@@ -6,17 +6,13 @@ Deploy content caching layer into K8s.
 
 ## Usage
 
-Build the charm:
+To deploy this charm into a k8s model:
 
-    `charmcraft build`
+    juju deploy cs:~content-cache-charmers/content-cache-k8s --config site=mysite.local --config backend=http://mybackend.local:80
 
-Deploy:
+And then you can test the deployment with:
 
-    `juju deploy ./content-cache.charm --config site=mysite.local --config backend=http://mybackend.local:80`
-
-### Test Deployment
-
-`curl --resolve mysite.local:80:<ingress IP> http://mysite.local`
+    curl --resolve mysite.local:80:<ingress IP> http://mysite.local
 
 ### Scale Out Usage
 
@@ -26,23 +22,28 @@ Just run `juju scale-application <application name> 3`.
 
 Build the docker image:
 
-    `git clone https://git.launchpad.net/charm-k8s-content-cache`
-    `cd charm-k8s-content-cache/docker`
-    `docker build . -t myimage:v<revision>`
-    `docker tag myimage:v<revision> localhost:32000/myimage:v<revision>`
-    `docker push localhost:32000/myimage:v<revision>`
+    git clone https://git.launchpad.net/charm-k8s-content-cache
+    cd charm-k8s-content-cache/docker
+    docker build . -t myimage:v<revision>
+    docker tag myimage:v<revision> localhost:32000/myimage:v<revision>
+    docker push localhost:32000/myimage:v<revision>
 
 Then, to use your new image, either replace the `deploy` step above with
 
-    `juju deploy ./content-cache.charm --config image_path=localhost:32000/myimage:v<revision> --config site=mysite.local --config backend=http://mybackend.local:80`
+    juju deploy cs:~content-cache-charmers/content-cache-k8s --config image_path=localhost:32000/myimage:v<revision> --config site=mysite.local --config backend=http://mybackend.local:80
 
 Or, if you have already deployed content-cache:
 
-    `juju config content-cache image_path=localhost:32000/myimage:v<revision>`
+    juju config content-cache image_path=localhost:32000/myimage:v<revision>
 
 ## Developing
 
-Just run `make lint`.
+To build the charm locally, just run `charmcraft build`. You can then deploy
+using:
+
+    juju deploy ./content-cache.charm
+
+To run lint against the code, run `make lint`.
 
 ## Testing