闭社主体 forked from https://github.com/tootsuite/mastodon
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Alexandra Catalina ba8a04462a
helm: upgrade elasticsearch chart to 14 (#15767)
7 months ago
..
templates helm: add support for S3 storage (#15748) 8 months ago
.helmignore Add Helm chart (#14090) 1 year ago
Chart.lock helm: upgrade elasticsearch chart to 14 (#15767) 7 months ago
Chart.yaml helm: upgrade elasticsearch chart to 14 (#15767) 7 months ago
readme.md helm: add support for S3 storage (#15748) 8 months ago
values.yaml helm: add support for S3 storage (#15748) 8 months ago

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.