Fork of https://gitlab.com/glitchtip/glitchtip-helm-chart to fix a bug in the upstream django-helm-chart
Find a file
David Burke a9ec70c244 Merge branch '5-more-generic-helm' into 'master'
Make helm chart more generic

Closes #5

See merge request glitchtip/glitchtip-helm-chart!1
2021-02-19 20:17:46 +00:00
charts postgresql and redis chart update 2021-01-23 15:49:40 -05:00
templates consistent deployment names 2021-02-15 16:43:28 -05:00
.gitlab-ci.yml Update chart path 2020-07-29 09:35:49 -04:00
.helmignore Initial commit 2020-01-14 22:04:41 -05:00
Chart.lock postgresql and redis chart update 2021-01-23 15:49:40 -05:00
Chart.yaml postgresql and redis chart update 2021-01-23 15:49:40 -05:00
LICENSE Add LICENSE 2020-11-20 16:46:31 +00:00
README.md Add README.md 2020-10-23 20:26:16 +00:00
values-sample.yaml Moving chart from glitchtip-frontend to here 2020-05-15 16:53:29 -04:00
values.yaml Update values.yaml with better defaults 2021-02-14 17:14:15 +00:00

GlitchTip Helm Chart

We use this chart internally. However it's not fully documented yet nor tested in a wide range of scenarios. If you are a helm and kubernetes expert - feel free to use this and help contribute to this repo.

Usage

  1. Add our Helm chart repo helm repo add glitchtip https://glitchtip.gitlab.io/glitchtip-helm-chart/
  2. Review our values.yaml. At a minimum you'll need to set databaseURL and secretKey.
  3. Install the chart helm install glitchtip/glitchtip --set databaseURL=your_db --set secretKey=random_string