A supported fork of Mastodon that provides local posting and a wider range of content types.
Go to file
2021-07-01 13:59:58 +02:00
.drone.yml Use new image namespace 2021-06-21 12:28:36 +02:00
.env.sample Comment out OIDC related env var by default 2021-06-23 15:55:00 +02:00
.gitignore Initial commit 2021-05-07 13:34:21 +02:00
abra.sh Bump versioned config 2021-07-01 13:59:58 +02:00
compose.oidc.yml Fix image usage 2021-06-23 14:02:26 +02:00
compose.yml Use new image 2021-06-23 15:46:29 +02:00
entrypoint.sh.tmpl Use templating to conditionally load this env var 2021-06-23 16:14:29 +02:00
README.md Note further config [ci skip] 2021-06-23 17:37:00 +02:00
renovate.json Add renovate.json 2021-06-04 07:01:59 +00:00

Hometown

A supported fork of Mastodon that provides local posting and a wider range of content types.

This repository is a copy of coop-cloud/mastodon but with a fresh README and some Hometown specific configuration. It seems like a good idea to keep the deployment separate since the apps may diverge in their deployment or configuration instructions at some point despite best wishes to remain as mainline Mastodon as possible.

Basic usage

  1. Set up Docker Swarm and abra
  2. Deploy coop-cloud/traefik
  3. abra app new mastodon
  4. Follow the secrets setup docs
  5. abra app YOURAPPDOMAIN config - be sure to change DOMAIN to something that resolves to your Docker swarm box
  6. abra app YOURAPPDOMAIN deploy to deploy the app

You'll need to run a docker exec -it <streaming-service-id> /bin/bash and do the following:

export OTP_SECRET=$(cat /run/secrets/otp_secret)
export SECRET_KEY_BASE=$(cat /run/secrets/secret_key_base)
export DB_PASS=$(cat /run/secrets/db_password)
bundle exec rake db:setup

Then, on your host (outside of the containers), you'll need to fix permissions for the volume (see #2):

chown -R 991:991 /var/lib/docker/volumes/<service-name>_app/_data

And finally, within any app container, create an admin account:

tootctl accounts create <username> --email <email> --confirmed --role admin

Secrets setup

Because Mastodon expects secrets generated by specific tools, we don't support that in abra yet. However, you can run these commands yourself using the underlying Docker CLI. You can then load them in as secrets to the swarm using abra though and then they will be picked up on the deployment.

First, generate the SECRET_KEY_BASE and OTP_SECRET and store them in your local shell environment, you'll need them for subsequent commands.

$ SECRET_KEY_BASE=$(docker run --rm tootsuite/mastodon:v3.4.0 bundle exec rake secret)
$ OTP_SECRET=$(docker run --rm tootsuite/mastodon:v3.4.0 bundle exec rake secret)
$ abra app YOURAPPDOMAIN secret insert secret_key_base v1 $SECRET_KEY_BASE
$ abra app YOURAPPDOMAIN secret insert otp_secret v1 $OTP_SECRET

Then you need to generate the VAPID_{PUBLIC/PRIVATE}_KEY values using the SECRET_KEY_BASE/OTP_SECRET:

$ docker run \
  -e SECRET_KEY_BASE=$SECRET_KEY_BASE \
  -e OTP_SECRET=$OTP_SECRET \
  --rm tootsuite/mastodon:v3.4.0 \
  bundle exec rake mastodon:webpush:generate_vapid_key

Once you see the values generated, you can load the VAPID_PUBLIC_KEY into your .env file and VAPID_PRIVATE_KEY into a secret.

$ abra app YOURDOMAIN secret insert vapid_private_key v1 YOURVAPIDPRIVATEKEY

And finally, to end your whirlwind secrets loading adventure, get the DB_PASS and SMTP_PASSWORD loaded.

$ abra app YOURAPPDOMAIN secret generate db_password v1
$ abra app YOURDOMAIN secret insert smtp_password v1 YOURSMTPPASSWORD