Issue #2:<\/h3>\n\n\n\nError: Database is uninitialized and superuser password is not specified.\nYou must specify POSTGRES_PASSWORD to a non-empty value for the\nsuperuser<\/pre>\n\n\n\nThis is caused by the pg_isready<\/code> healthcheck failing and can be fixed by setting the necessary env variables in docker-compose.yml<\/code>. The resulting db<\/code> compose service looks as follows:<\/p>\n\n\n\ndb:\n restart: always\n image: postgres:9.6-alpine\n shm_size: 256mb\n networks:\n - internal_network\n healthcheck:\n test: [\"CMD\", \"pg_isready\", \"-U\", \"mastodon\", \"-d\", \"mastodon_production\"]\n volumes:\n - .\/postgres:\/var\/lib\/postgresql\/data\n environment:\n POSTGRES_PASSWORD: xyz\n POSTGRES_DB: mastodon_production\n POSTGRES_USER: mastodon\n<\/code><\/pre>\n\n\n\nOptional features enabled by default<\/h2>\n\n\n\ns3 object storage<\/h3>\n\n\n\n
This is enabled by default in the sample environment file. If you don’t configure it correctly (or forget to turn it off), you’ll notice that media uploads are failing. The failures are accompanied by the following log message: method=POST path=\/api\/v2\/media format=html controller=Api::V2::MediaController action=create status=500 error='Aws::Sigv4::Errors::MissingCredentialsError: missing credentials,provide credentials with one of the following options<\/code>. <\/p>\n\n\n\nIf you want to store media on local storage, just comment the lines under File Storage in the env file. Do check to ensure that \/opt\/mastodon\/public\/system\/<\/code> in the web container is persisted on the host system (this should be case via the volume defined in the docker-compose.yml<\/code>).<\/p>\n\n\n\nelastic search<\/h3>\n\n\n\n
Elastic search is also enabled by default in the sample env file, while it is commented out in the docker-compose.yml<\/code> file. If you don’t have the es<\/code> containter running, you’ll notice a large number of sidekiq jobs starting to accumulate in the ‘Retry’ state with the following error message: Faraday::ConnectionFailed: Failed to open TCP connection to localhost:9200 (Cannot assign requested address - connect(2) for \"localhost\" port 9200)<\/code>. Either enable the es<\/code> container or comment out ES_ENABLED=true<\/code> in the ENV file.<\/p>\n\n\n\nMy entire ENV file<\/h2>\n\n\n\n
For completeness you can find my entire .env.production<\/code> file below, where sensitive entries have been redacted. Note I am currently using mailgun as an SMTP server, as I found sendgrid to be blocked by Spam filters. <\/p>\n\n\n\n# This is a sample configuration file. You can generate your configuration\n# with the `rake mastodon:setup` interactive setup wizard, but to customize\n# your setup even further, you'll need to edit it manually. This sample does\n# not demonstrate all available configuration options. Please look at\n# https:\/\/docs.joinmastodon.org\/admin\/config\/ for the full documentation.\n\n# Federation\n# ----------\n# This identifies your server and cannot be changed safely later\n# ----------\nLOCAL_DOMAIN=social.vdna.be\n\n# Redis\n# -----\nREDIS_HOST=mastodon_redis_1\nREDIS_PORT=6379\n\n# PostgreSQL\n# ----------\nDB_HOST=mastodon_db_1\nDB_USER=mastodon\nDB_NAME=mastodon_production\nDB_PASS=xyz\nDB_PORT=5432\n\n# ElasticSearch (optional)\n# ------------------------\n# ES_ENABLED=true\n# ES_HOST=localhost\n# ES_PORT=9200\n\n# Secrets\n# -------\n# Make sure to use `rake secret` to generate secrets\n# -------\nSECRET_KEY_BASE=xyz\nOTP_SECRET=xyz\n\n# Web Push\n# --------\n# Generate with `rake mastodon:webpush:generate_vapid_key`\n# --------\nVAPID_PRIVATE_KEY=xyz\nVAPID_PUBLIC_KEY=xyz\n\n# Sending mail\n# ------------\nSMTP_SERVER=smtp.eu.mailgun.org\nSMTP_PORT=587\nSMTP_LOGIN=postmaster@mg.social.vdna.be\nSMTP_PASSWORD=xyz\nSMTP_FROM_ADDRESS=social@mg.social.vdna.be\n\n# File storage (optional)\n# -----------------------\n#S3_ENABLED=true\n#S3_BUCKET=files.example.com\n#AWS_ACCESS_KEY_ID=\n#AWS_SECRET_ACCESS_KEY=\n#S3_ALIAS_HOST=files.example.com<\/pre>\n","protected":false},"excerpt":{"rendered":"Recently I’ve setup an invite-only mastodon instance as a private space for friends and family. While I am still evaluating whether mastodon is the right tool for such a private space, I’d like to share a number of issues I encountered during setup.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,4],"tags":[],"class_list":["post-327","post","type-post","status-publish","format-standard","hentry","category-linux","category-software","entry"],"_links":{"self":[{"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/posts\/327","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/comments?post=327"}],"version-history":[{"count":5,"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/posts\/327\/revisions"}],"predecessor-version":[{"id":338,"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/posts\/327\/revisions\/338"}],"wp:attachment":[{"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/media?parent=327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/categories?post=327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vdna.be\/site\/index.php\/wp-json\/wp\/v2\/tags?post=327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Mastodon](\"https:\/\/upload.wikimedia.org\/wikipedia\/commons\/thumb\/b\/b4\/Mastodon_Mascot.png\/220px-Mastodon_Mascot.png\")
Recently I’ve setup an invite-only mastodon instance as a private space for<\/p>\n