From 9e7253f01a2e0ea46bbbadc7de9fb336fbe7b67b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20=27rysiek=27=20Wo=C5=BAniak?=
 <rysiek@hackerspace.pl>
Date: Thu, 4 Apr 2019 13:16:22 +0200
Subject: [PATCH] README changes

---
 README.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c597773..4f52532 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,8 @@
 
 A front-end cache and reverse proxy config, based on `nginx`, with Tor thrown in for good measure.
 
+Please treat this as a blueprint for your deployment.
+
 ## Idea
 
 The basic idea is to have a minimal front-end-cache config that can be spun-up (or indeed, that's just running) on a public server and is able to cache and serve a WordPress website effectively.
@@ -58,4 +60,5 @@ But we did look at `varnish`, and we found [it does not support SSL and has no i
 
 # ToDo
 
-This needs to be documented better, both using comments in code, and using this README file, and the one in the `services/etc/nginx` subdirectory.
+ - This needs to be documented better, both using comments in code, and using this README file, and the one in the `services/etc/nginx` subdirectory.
+ - Also, cleanups in the `nginx` config, there is a lot of unnecessary repetition
-- 
GitLab