Skip to content

Latest commit

 

History

History
81 lines (61 loc) · 2.72 KB

README.md

File metadata and controls

81 lines (61 loc) · 2.72 KB

Mastodon Argo CD Application(Set)s Templates

Mastodon is social networking that's not for sale.

NOTE: This chart is still now working due to #20901 not being merged, and the issues #20904 and #20902. After those are fixed, we'll take another stab at making the bitnami chart work.

We create in the manifests and helm chart in this sync wave order:

  • All External Secrets
  • postgresql, redis, elasticsearch
  • Mastodon Web Appset

Creating Mastodon Secrets

This template relies on you already having created secrets using the below method and then creating those as k8s secrets.

SECRET_KEY_BASE=$(docker run --rm -it tootsuite/mastodon:latest bin/rake secret)
OTP_SECRET=$(docker run --rm -it tootsuite/mastodon:latest bin/rake secret)

docker run --rm -e "OTP_SECRET=$OTP_SECRET" \
    -e "SECRET_KEY_BASE=$SECRET_KEY_BASE" \
    -it tootsuite/mastodon:latest bin/rake mastodon:webpush:generate_vapid_key

Connect to postgres with worker container

Deploy the following container and attach to the shell, then run:

apiVersion: v1
kind: Pod
metadata:
  name: debug-container
  namespace: mastodon
spec:
  containers:
  - name: postgres-client
    image: ubuntu:latest
    command:
      - sleep
      - "3600"
    imagePullPolicy: IfNotPresent
  restartPolicy: Always

Run the following to install utilities

apt-get update && apt-get install -y postgresql-client dnsutils curl

connection string format:

psql -U mastodon \
  -d mastodon \
  -h mastodon-postgres.mastodon.svc.cluster.local \
  -p 5432

relation "accounts" does not exist error in the logs:

You may need to generate a DB migrate job from a helm template command as per suggestion in issue#18

Unsupported value for canned acl 'public-read'

redacted exact paths for security

[paperclip] saving accounts/avatars/../original/5eb5eab423667b38.png

method=PUT path=/settings/profile format=html controller=Settings::ProfilesController action=update status=500 error='Aws::S3::Errors::InvalidArgument: Unsupported value for canned acl 'public-read'' duration=368.45 view=0.00 db=1.15

Aws::S3::Errors::InvalidArgument (Unsupported value for canned acl 'public-read'):

pretty sure this was due to the bucket not having public read :)

admin commands

To get a shell into the main mastodon container:

kubectl exec deploy/mastodon-web-app -- /bin/bash

tootctl commands can then be run as normal. Checkout the mastodon docs for more!