specter/mastodon
1
0
Fork 0
forked from fedi/mastodon
Code Pull requests Activity
mastodon/chart
History
Alex Dunn 9c273c2a59
helm: standardize yaml configuration (#15728) 
- move application variables under `mastodon` namespace
- restore standard yaml structure for ingress configuration
- move values.yaml.template to values.yaml
2021-02-15 08:00:54 +01:00
..
templates helm: standardize yaml configuration (#15728) 2021-02-15 08:00:54 +01:00
.helmignore Add Helm chart (#14090) 2020-06-29 13:58:48 +02:00
Chart.yaml helm: standardize yaml configuration (#15728) 2021-02-15 08:00:54 +01:00
readme.md helm: standardize yaml configuration (#15728) 2021-02-15 08:00:54 +01:00
values.yaml helm: standardize yaml configuration (#15728) 2021-02-15 08:00:54 +01:00

readme.md

Introduction

This is a Helm chart for installing Mastodon into a Kubernetes cluster. The basic usage is:

  1. edit values.yaml or create a separate yaml file for custom values
  2. helm dep update
  3. helm install --namespace mastodon --create-namespace my-mastodon ./ -f path/to/additional/values.yaml

This chart has been tested on Helm 3.0.1 and above.

Configuration

The variables that must be configured are:

  • password and keys in the mastodon.secrets, postgresql, and redis groups; if left blank, some of those values will be autogenerated, but will not persist across upgrades.

  • SMTP settings for your mailer in the mastodon.smtp group.

Missing features

Currently this chart does not support:

  • Hidden services
  • S3/Minio/GCS
  • Single Sign-On
  • Swift
  • configurations using WEB_DOMAIN

Upgrading

Because database migrations are managed as a Job separate from the Rails and Sidekiq deployments, it’s possible they will occur in the wrong order. After upgrading Mastodon versions, it may sometimes be necessary to manually delete the Rails and Sidekiq pods so that they are recreated against the latest migration.