infra/mastodon-chart
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
23 Commits 1 Branch 0 Tags 200 KiB
Smarty 100%
566b80bd41
Go to file
Takuya Yoshida 566b80bd41 Add support >= 1.22 (#17490)
2022-02-09 12:30:00 +01:00
templates Add support >= 1.22 (#17490) 2022-02-09 12:30:00 +01:00
.helmignore Add Helm chart (#14090) 2020-06-29 13:58:48 +02:00
Chart.lock Update Helm release elasticsearch to v15.10.3 (#16651) 2021-10-14 21:01:27 +02:00
Chart.yaml helm: upgrade elasticsearch to 7.x (#17262) 2022-01-09 03:21:19 +01:00
LICENSE Fix #49 - License changed from GPL-2.0 to AGPL-3.0 2016-09-21 23:04:34 +02:00
readme.md helm: add support for S3 storage (#15748) 2021-02-19 09:52:32 +01:00
values.yaml Update tootsuite/mastodon Docker tag to v3.4.6 (#17436) 2022-02-03 21:29:20 +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
  • 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.