started updating the README

README.md

@@ -6,14 +6,14 @@ This is meant to provide an easy way to install [CLARIN DSpace](https://github.c
 
 You need a Linux server (we tested on Ubuntu 16.04 and CentOS 7.3) with a recent install of Docker (we tested with 17.05.0-ce) or a Kubernetes cluster (we are using version 1.8). Clone this git repository onto the server. Then you need to look through all the files in commul-customization and adapt the configuration to your server (domain name, user names, etc).
 
-None of the files contain passwords, instead passwords and other confidential information is using environment variables. In Kubernetes you can use [secrets](https://kubernetes.io/docs/concepts/configuration/secret/) for this.
+None of the files contain passwords, instead passwords and other confidential information are provided to the containers using environment variables. In Kubernetes you can use [secrets](https://kubernetes.io/docs/concepts/configuration/secret/) for this.
 
 # Exemplary workflow using Docker Compose
 
 ## get Dockerfiles
 ```
-git clone https://github.com/commul/clarin-dspace-docker
-cd clarin-dspace-docker
+git clone https://gitlab.inf.unibz.it/commul/docker/clarin-dspace/
+cd clarin-dspace
 ```
 
 ## get my versions of dist files
@@ -42,7 +42,7 @@ docker-compose up -d --build
 
 ## enter the DSpace container
 ```
-docker exec -ti clarindspacedocker_dspace_1 bash
+docker exec -ti clarindspace_dspace_1 bash
 ```
 
 ## deploy DSpace
@@ -67,49 +67,48 @@ cd /opt/repository/sources/dspace/utilities/project_helpers/scripts
 /etc/init.d/tomcat8 start
 ```
 
-# DSpace directory structure
+# Kubernetes
 
-This is the directory structure
+
+## Prerequisites
+
+* Kubernetes cluster
+* Kubernetes credentials
+* a working [kubectl] (https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+
+# Workflow
+
+## Building docker images
+Kubernetes is pulling images from a registry, so you need to first build the docker files. We try to keep the version numbers of all images in sync and use the script [release.sh](dockerfiles/release.sh) for this. It takes the new version number as its argument and builds all docker images and pushes them into our registry. You will need to edit this script and exchange the registry URL with your own.
+
+## deploying to Kubernetes
+
+After pushing all images to your container registry you can ask Kubernetes to pull and deploy them. If necessary, you might need to create a [personal token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) for logging into the GitLab Registry and store it as a secret that you then reference in the Kubernetes yaml files.
+
+There is a handy script that calls all necessary kubectl commands one after another called [start-kube.sh](kubernetes/start-kube.sh), for bringing it all down again use [stop-kube.sh](kubernetes/stop-kube.sh) instead. For this to work, make sure that you have the correct images referenced in the deployment yaml files.
 
 ```
-├── clarin-dspace-docker
-│   └── commul-customization
-└── kubernetes
-    ├── helm
-    │   └── dspace
-    │       ├── charts
-    │       │   └── postgresql
-    │       │       └── templates
-    │       └── templates
-    └── yaml
+image: gitlab.inf.unibz.it:4567/commul/docker/clarin-dspace/staging/dspace:1.2-RC1
 ```
 
 
-* `/clarin-dspace-docker` - Docker files, copied from https://github.com/commul/clarin-dspace-docker @ 74d06d3 . **With this directory, you can build images**
-* `/kubernetes/helm` - Chart Directory. Refer to https://github.com/kubernetes/helm/blob/master/docs/charts.md#the-chart-file-structure :exclamation: **not working yet** :exclamation:
-* `/kubernetes/yaml` - Useful for tests, but helm is a more flexible approach **With this directory, you can deploy images in kubernetes cluster**
-# Introduction
-# Prerequisites
 
-* Kubernetes cluster
 
-## To interact with cluster
 
-* Kubernetes credentials
-* a working [kubectl] (https://kubernetes.io/docs/tasks/tools/install-kubectl/)
 
-# How to use it
-## Workflow
 
-Kubernetes is pulling images from a registry, so you need to first build the docker files. We try to keep the version numbers of all images in sync and use the script [release.sh](dockerfiles/release.sh) for this. It takes the new version number as its argument and builds all docker images and pushes them into our registry. You will need to edit this script and exchange the registry URL with your own.
+ceph
+
+secrets
+
+
+
+
+
+
+d
 
-First of all, check if a docker image already exists.
-If it exist, pull, otherwise, you need to build one.
-If necessary create a [personal token](https://gitlab.scientificnet.org/profile/personal_access_tokens) and login into GitLab Registry.
 
-```console
-docker login gitlab.scientificnet.org:4567
-```
 
 ### Use existing Docker image
 ```console