@@ -4,14 +4,24 @@ Repository to keep helm charts for the overture projects.
44
55# How to package and publish:
66
7- - Turn a chart into a versioned chart archive file
7+ - Bump the chart version following SemVer standards
8+ - Turn a chart into a versioned chart archive file
89
910```
10- helm package ./mychart
11+ helm package ./mychart
1112```
1213
13- - then copy the chart to the charts-server repository (another git repository in overture-stack)
14- - then you need to reindex — see charts-server for instructions.
14+ - See the [ charts-server's ReadMe] ( https://github.com/overture-stack/charts-server ) for further instructions.
15+
16+ ### Implementation notes:
17+
18+ - You're able to test your changes locally through
19+
20+ ```
21+ helm template <packaged chart or folder> <optionally: -f values.yaml>
22+ ```
23+
24+ ---
1525
1626# Upgrade notes
1727
@@ -20,15 +30,15 @@ helm package ./mychart
2030This app now uses Helm configMaps to store a few config files.
2131When the chart is deployed the following configmaps are created, containing these files:
2232
23- ### In Server (formerly API), ` arranger-server-configs `
33+ ### In Server (formerly " API" ), ` arranger-server-configs `
2434
25- - base.json
26- - extended.json
27- - facets.json
28- - matchbox.json
29- - table.json
35+ - base.json
36+ - extended.json
37+ - facets.json
38+ - matchbox.json
39+ - table.json
3040
31- Each of these default to ` {} ` , and should customised by passing values into helm in the follwowing fashion
41+ Each of these default to ` {} ` , and should customized by passing values into helm in the following fashion
3242
3343```
3444serverConfigs: {
@@ -40,8 +50,8 @@ serverConfigs: {
4050
4151### And in Admin UI, ` arranger-nginx-config `
4252
43- - nginx.conf
44- - env-config.js
53+ - nginx.conf
54+ - env-config.js
4555
4656| Customizable parameter | Description | Default |
4757| -------------------------- | ----------------- | ------- |
0 commit comments