Pleromaの設定@2019-07-09

prod.secret.exs

# Pleroma instance configuration

# NOTE: This file should not be committed to a repo or otherwise made public
# without removing sensitive information.

use Mix.Config

config :pleroma, Pleroma.Web.Endpoint,
   url: [host: "v01d.app", scheme: "https", port: 443],
   secret_key_base: "[REDACTED]"

config :pleroma, :instance,
  name: "V01D.app",
  email: "admin@v01d.app",
  description: "VOID TALK...",
  limit: 5000,
  registrations_open: true,
  dedupe_media: false

config :pleroma, :media_proxy,
  enabled: true,
  base_url: "https://cache.v01d.app",
  proxy_opts: [
    # inline_content_types: [] | false | true,
    http: [
      follow_redirect: true,
      pool: :media
    ],
    redirect_on_failure: true,
    keep_user_agent: true
  ]

# Configure your database
config :pleroma, Pleroma.Repo,
  adapter: Ecto.Adapters.Postgres,
  username: "v01dapp",
  password: "[REDACTED]",
  database: "v01dapp",
  hostname: "10.0.0.1",
  pool_size: 50

# Configure web push notifications
config :web_push_encryption, :vapid_details,
  subject: "mailto:admin@v01d.app",
  public_key: "[REDACTED]",
  private_key: "[REDACTED]"

config :pleroma, :gopher,
  enabled: false,
  ip: {0, 0, 0, 0},
  port: 9999

config :pleroma, :suggestions,
  enabled: false,
  third_party_engine:
    "http://vinayaka.distsn.org/cgi-bin/vinayaka-user-match-suggestions-api.cgi?{{host}}+{{user}}",
  timeout: 300_000,
  limit: 23,
  web: "https://vinayaka.distsn.org/?{{host}}+{{user}}"

# Enable Strict-Transport-Security once SSL is working:
config :pleroma, :http_security,
  sts: true

# Configure S3 support if desired.
# The public S3 endpoint is different depending on region and provider,
# consult your S3 provider's documentation for details on what to use.
#
config :pleroma, Pleroma.Uploaders.S3,
  bucket: "media.v01d.app",
  public_endpoint: "https://"
#
# Configure S3 credentials:
config :ex_aws, :s3,
  access_key_id: "[REDACTED]",
  secret_access_key: "[REDACTED]",
  region: "us-east-1",
  scheme: "https://"
#
# For using third-party S3 clones like wasabi, also do:
config :ex_aws, :s3,
  host: "s3.us-west-1.wasabisys.com"


# Configure Openstack Swift support if desired.
#
# Many openstack deployments are different, so config is left very open with
# no assumptions made on which provider you're using. This should allow very
# wide support without needing separate handlers for OVH, Rackspace, etc.
#
# config :pleroma, Pleroma.Uploaders.Swift,
#  container: "some-container",
#  username: "api-username-yyyy",
#  password: "api-key-xxxx",
#  tenant_id: "<openstack-project/tenant-id>",
#  auth_url: "https://keystone-endpoint.provider.com",
#  storage_url: "https://swift-endpoint.prodider.com/v1/AUTH_<tenant>/<container>",
#  object_url: "https://cdn-endpoint.provider.com/<container>"
#

config :pleroma, Pleroma.Upload,
  uploader: Pleroma.Uploaders.S3,
  base_url: "https://cache.v01d.app",
  filters: [Pleroma.Upload.Filter.Dedupe,Pleroma.Upload.Filter.AnonymizeFilename,Pleroma.Upload.Filter.Mogrify],
  proxy_remote: false,
  proxy_opts: []

# Strip Exif
# Also put Pleroma.Upload.MogrifyFilter in the `filters` list of Pleroma.Upload configuration.
config :pleroma, Pleroma.Upload.Filter.Mogrify,
  args: "strip"
#  Pleroma.Upload.MogrifyFilter: [args: "strip"]

config :pleroma, :http,
      proxy_url: "localhost:8118"

config :pleroma, Pleroma.Emails.Mailer,
  adapter: Swoosh.Adapters.SMTP,
  relay: "m.zxc.st",
  username: "admin@v01d.app",
  password: "[REDACTED]",
  port: 465,
  ssl: true,
  tls: :always,
  auth: :always

config :pleroma, Pleroma.Captcha,
  enabled: true,
  method: Pleroma.Captcha.Kocaptcha

config :pleroma, Pleroma.Captcha.Kocaptcha,
  endpoint: "https://captcha.kotobank.ch"

config :pleroma, Pleroma.Web.Federator.RetryQueue,
  enabled: true,
  max_jobs: 30,
  max_retries: 10