molgenis/thirdparty-ops-docker-helm
7
0
Fork 1
Code Issues Pull Requests Releases Wiki Activity

[CHORE] updated docs for website chart #12

Merged
S. Haakma merged 1 commits from p281392/thirdparty-ops-docker-helm:master into master 2018-11-30 07:49:01 +01:00
Conversation 0 Commits 1 Files Changed 2 +5 -5
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
charts/molgenis-website/Chart.yaml
View File

@ -1,8 +1,8 @@
apiVersion: v1 apiVersion: v1
appVersion: "1.0" appVersion: "1.0"
description: MOLGENIS Helm chart for OpenCPU description: MOLGENIS Helm chart for the website
name: molgenis-website name: molgenis-website
version: 0.3.2 version: 0.3.3
sources: sources:
- https://git.webhosting.rug.nl/molgenis/thirdparty-ops-docker-helm.git - https://git.webhosting.rug.nl/molgenis/thirdparty-ops-docker-helm.git
icon: https://git.webhosting.rug.nl/molgenis/thirdparty-ops-docker-helm/raw/master/charts/molgenis-website/catalogIcon-molgenis-website.png icon: https://git.webhosting.rug.nl/molgenis/thirdparty-ops-docker-helm/raw/master/charts/molgenis-website/catalogIcon-molgenis-website.png

6
charts/molgenis-website/README.md
View File

@ -1,6 +1,6 @@
# MOLGENIS - OpenCPU Helm Chart # MOLGENIS - Website Helm Chart
NEXUS repository for kubernetes to deploy on a kubernetes cluster with NFS-share Website Helm chart to deploy the molgenis.org website.
## Containers ## Containers
@ -9,7 +9,7 @@ This chart will deploy the following containers:
- NGINX - NGINX
## Provisioning ## Provisioning
You can choose for the OpenCPU image from which repository you want to pull. Experimental builds are pushed to registry.molgenis.org and the stable builds to hub.docker.com. You can choose which version of the NGINX image you want to deploy. Each merge with the master results in a tagged image with the build-number.
You need to fill out 2 properties to determine which repository you are going to use. You need to fill out 2 properties to determine which repository you are going to use.
- ```site.image.repository``` - ```site.image.repository```