Your self-hosted, globally interconnected microblogging community
Go to file
KawaiiPunk 0168577d65
continuous-integration/drone/push Build is failing Details
chore: publish 0.1.2+v4.1.4 release
2023-07-10 14:15:15 +01:00
.drone.yml Switch to self-hosted stack-ssh-deploy image [mass update] 2023-01-21 11:49:56 -08:00
.env.sample wip: v4.x & major config refactor 2023-02-15 01:30:24 +01:00
.gitignore Initial commit 2021-05-07 13:34:21 +02:00 docs: more commands, less quotes [ci skip] 2023-02-17 09:51:21 +01:00 fix: use RAILS_ENV in setup script [ci skip] 2023-02-17 10:03:58 +01:00
compose.yml chore: publish 0.1.2+v4.1.4 release 2023-07-10 14:15:15 +01:00 fix: migrate latest hometown changes [ci skip] 2023-02-15 20:16:16 +01:00


Your self-hosted, globally interconnected microblogging community

  • Category: Apps
  • Status: 1
  • Image: tootsuite/mastodon
  • Healthcheck: No
  • Backups: No
  • Email: Yes
  • Tests: No
  • SSO: Yes

Quick start

Mastodon expects secrets to be formatted in a very specific way, so please choose "No" when prompted to generate secrets for abra app new mastodon. The secrets must be generated outside of abra and that is achieved in step 2. See the for more.

  1. abra app new mastodon
  2. abra app cmd <domain> secrets --local
  3. abra app secret insert <domain> smtp_password v1 <password>
  4. abra app config <domain> (uncomment SMTP details)
  5. abra app deploy <domain>
  6. abra app cmd <domain> streaming setup

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

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

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

abra app cmd <domain> admin -- <username> <email>

Tips & tricks

Auto-complete is not working?

Check the sidekiq logs (/sidekiq/retries), is a bunch of stuff failing? What is the error?

If it looks anything like blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; then it might mean that your elastic search service has put itself into "read-only" state. This could be due to running close to no free disk space one time. ES doesn't undo this state, even when you have more free disk space once more, so you need to handle this manually:

abra app run <domain> es bash
curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

Then head back to the sidekiq retries panel and retry one job. You should see the ticket of retries go down by one if if passed. Then you can "retry all" and they should get scheduled & run.