Removed bootstrap.memory_lock=true parameter form elasticsearch service

#19
fititnt · Oct 16, 2018 · e4ccbbf · e4ccbbf
1 parent 5d0ff78
commit e4ccbbf
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -18,10 +18,9 @@ services:
   elasticsearch:
     image: docker.elastic.co/elasticsearch/elasticsearch:5.5.3
     restart: unless-stopped
-    command: elasticsearch -Expack.security.enabled=false -Ecluster.name=docker-cluster -Ebootstrap.memory_lock=true -Ehttp.port=9200 -Ehttp.cors.allow-origin="http://localhost:51000" -Ehttp.cors.enabled=true -Ehttp.cors.allow-headers=X-Requested-With,X-Auth-Token,Content-Type,Content-Length,Authorization -Ehttp.cors.allow-credentials=true
+    command: elasticsearch -Expack.security.enabled=false -Ecluster.name=docker-cluster -Ehttp.port=9200 -Ehttp.cors.allow-origin="http://localhost:51000" -Ehttp.cors.enabled=true -Ehttp.cors.allow-headers=X-Requested-With,X-Auth-Token,Content-Type,Content-Length,Authorization -Ehttp.cors.allow-credentials=true
     environment:
       - cluster.name=docker-cluster
-      - bootstrap.memory_lock=true
       - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
       - xpack.security.enabled=false
     ulimits:

diff --git a/production-instructions.md b/production-instructions.md
@@ -1,4 +1,4 @@
-# Use of Uwazi production enviroment
+# Use of Uwazi in production environment
 > Disclaimer: [uwazi-docker](https://github.com/fititnt/uwazi-docker) can make it
 easy for someone unskilled test [Uwazi](https://www.uwazi.io/) and, at best,
 in hands with someone with a knowledge of docker/databases and free time, be a