Merge branch 'rename-package' into 'helm'

Rename package

See merge request !23

.gitignore

@@ -21,4 +21,5 @@
 *.tmproj
 .vscode/
 rshiny-*.tgz
-shiny-server-*.tgz
+shiny-server-*.tgz
\ No newline at end of file
+shiny-k8s-toolkit-helm-*.tgz
\ No newline at end of file

.gitlab-ci.yml

@@ -5,8 +5,8 @@ upload:
   needs: []
   image: harbor.pasteur.fr/kube-system/helm-kubectl:3.4.0
   script:
-    - CHART_VERSION=$(helm show chart shiny-server | grep version | cut -d' ' -f2)
-    - CHART_NAME=$(helm show chart shiny-server | grep name | cut -d' ' -f2)
+    - CHART_VERSION=$(helm show chart shiny-k8s-toolkit-helm | grep version | cut -d' ' -f2)
+    - CHART_NAME=$(helm show chart shiny-k8s-toolkit-helm | grep name | cut -d' ' -f2)
     - |
       if [ "helm" == "${CI_COMMIT_REF_SLUG}" ]; then
         export CHANNEL="stable"
@@ -14,7 +14,7 @@ upload:
         export CHANNEL="${CI_COMMIT_REF_SLUG}"
       fi
       echo $CHANNEL
-    - helm package shiny-server
+    - helm package shiny-k8s-toolkit-helm
     - curl --request POST --user gitlab-ci-token:$CI_JOB_TOKEN --form "chart=@${CHART_NAME}-${CHART_VERSION}.tgz" "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/helm/api/${CHANNEL}/charts"
 
 

README.md

@@ -2,11 +2,11 @@
 
 To build a package locally, and test it with the example project, you can do:
 ```sh
-helm package shiny-server -d ../*shiny-k8s-example-python/chart/charts/
-helm package shiny-server -d ../*shiny-k8s-example-r/chart/charts/
+helm package shiny-k8s-toolkit-helm -d ../*shiny-k8s-example-python/chart/charts/
+helm package shiny-k8s-toolkit-helm -d ../*shiny-k8s-example-r/chart/charts/
 ```
 
 It will store the package in the appropriate folder, and when you will run 
 `./dohelm.sh` the newest version will be used.
 
-Don't forget to increment the version counter in shiny-server/Chart.yaml
+Don't forget to increment the version counter in shiny-k8s-toolkit-helm/Chart.yaml

shiny-server/Chart.yaml → shiny-k8s-toolkit-helm/Chart.yaml

 apiVersion: v2
-name: shiny-server
+name: shiny-k8s-toolkit-helm
 description: A Helm chart for deploying shiny app in Kubernetes
 
 # A chart can be either an 'application' or a 'library' chart.
@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.7.5
+version: 0.8.0
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to