Whether to accept incoming block activities from other instances
+Whether blocks result in people getting unfollowed
+Whether to federate blocks to other instances
+Sign object fetches with HTTP signatures
+Whether to disallow following an account that has blocked the user in question
+Authentication form template. By default it's + show.html which corresponds to + lib/pleroma/web/templates/o_auth/o_auth/show.html.eex. +
+OAuth consumer mode authentication form template. By default it's + consumer.html which corresponds to + lib/pleroma/web/templates/o_auth/o_auth/consumer.html.eex. +
+The list of enabled OAuth consumer strategies; by default it's set by + OAUTH_CONSUMER_STRATEGIES + environment variable. You can enter values in the following format: 'a:foo b:baz' +
+Enables LDAP authentication
+LDAP server hostname
+LDAP port, e.g. 389 or 636
+True to use SSL, usually implies the port 636
+True to start TLS, usually implies the port 389
+LDAP base, e.g. 'dc=example,dc=com'
+LDAP attribute name to authenticate the user, e.g. when + 'cn', the filter will be 'cn=username,base' +
+The lifetime in seconds of the access token
+Keeps old refresh token or generate new refresh token when to obtain an access token
+Enable a background job to clean expired oauth tokens. Defaults to false.
+Interval to run the job to clean expired tokens. Defaults to 24 hours.
+Specify the class to be added to the generated link. False to clear.
+Specify the class to be added to the generated link. False to clear.
+Override the rel attribute. False to clear
+Override the rel attribute. False to clear
+Set to false to remove target='_blank' attribute
+Set to true to link urls with schema http://google.com
+Set to a number to truncate urls longer then the number. + Truncated urls will end in ..
+Specify the class to be added to the generated link. False to clear.
+Strip the scheme prefix
+Link urls with rarely used schemes (magnet, ipfs, irc, etc.)
+Whether the captcha should be shown on registration
+The time in seconds for which the captcha is valid
+The method/service to use for captcha
+Kocaptcha is a captcha service with a single API endpoint, the source code is + here. + The default endpoint 'https://captcha.kotobank.ch' is hosted by the developer. +
+RUM indexes are an alternative indexing scheme that is not included in PostgreSQL by default. + While they may eventually be mainlined, for now they have to be installed as a PostgreSQL extension from + + https://github.com/postgrespro/rum. + +
+Their advantage over the standard GIN indexes is that they allow efficient ordering of search results by timestamp, + which makes search queries a lot faster on larger servers, by one or two orders of magnitude. + They take up around 3 times as much space as GIN indexes.
+To enable them, both the rum_enabled flag has to be set and the following special + migration has to be run: mix ecto.migrate --migrations-path priv/repo/optional_migrations/rum_indexing/
+The name of the Repo supervisor process
+The directory where to keep repository data, like migrations, schema and more. Defaults to + priv/YOUR_REPO. It must always point to a subdirectory inside the priv directory
+An URL that specifies storage information
+The log level used when logging the query with Elixir's Logger
+The size of the pool used by the connection module. Defaults to 10
+Server hostname
+Connect to Postgres via UNIX sockets in the given directory. The socket name is derived based on the port. + This is the preferred method for configuring sockets and it takes precedence over the hostname. + If you are connecting to a socket outside of the Postgres convention, use :socket instead.
+Connect to Postgres via UNIX sockets in the given path. This option takes precedence over the + :hostname and :socket_dir
+Server port (default: 5432)
+The database to connect to
+Specifies the name of the database to connect to when creating or dropping the database. Defaults to "postgres"
+The connection pool module, defaults to DBConnection.ConnectionPool
+Set to true if ssl should be used
+The timeout for establishing new connections. Defaults to 5000
+How to prepare queries, either :named to use named queries or + :unnamed to force unnamed queries (default: :named)
+Enables code reloading functionality
+Enables using Plug.Debugger functionality for debugging failures in the application. + Recommended to be set to true only in development as it allows listing of the application source code during debugging. Defaults to false.
+A path to a json manifest file that contains static files and their digested version. + This is typically set to 'priv/static/cache_manifest.json' + which is the file automatically generated by mix phx.digest
+You can type in Elixir code here
+The port to run the server. Defaults to 4000 (http) and 4040 (https).
+The ip to bind the server to
+The reference name to be used. Defaults to plug.HTTP (http) and + plug.HTTPS (https). This is the value that needs to be given on shutdown.
+Cowboy will attempt to compress the response body. Defaults to false.
+Time in s with no requests before Cowboy closes the connection. Defaults to 5 s.
+You can type in Elixir code here
+The port to run the server. Defaults to 4000 (http) and 4040 (https).
+The ip to bind the server to
+The reference name to be used. Defaults to plug.HTTP (http) and + plug.HTTPS (https). This is the value that needs to be given on shutdown.
+Cowboy will attempt to compress the response body. Defaults to false.
+Time in s with no requests before Cowboy closes the connection. Defaults to 5 s.
+A secret key used as a base to generate secrets for encrypting and signing data. For example, cookies and tokens are signed by default, but they may also be encrypted if desired. Defaults to nil as it must be set per application
+When true, starts the web server when the endpoint supervision tree starts. Defaults to false. The mix phx.server task automatically sets this to true.
+The host without the scheme and a post (e.g example.com, not https://example.com:2020)
+e.g http, https
+Before enabling this you must: +
You can input relative path here
+Feel free to adjust the priv_dir and port number. + Then you will have to create the key for the keys (in the example priv/ssh_keys) and create the host keys with + ssh-keygen -m PEM -N "" -b 2048 -t rsa -f ssh_host_rsa_key. + After restarting, you should be able to connect to your Pleroma instance with ssh username@server -p $PORT +
+This form can be used to configure a keyword list that keeps the configuration data for any kind of frontend. + By default, settings for pleroma_fe and masto_fe are configured. + If you want to add your own configuration your settings need to be complete as they will override the defaults.
+Which theme to use
+or
+URL of the background, unless viewing a user profile with a background that is set
+or
+URL of the logo
+Whether to use only the logo's shape as a mask (true) or as a regular image (false)
+What margin to use around the logo
+Relative URL which indicates where to redirect when a user is logged in
+Relative URL which indicates where to redirect when a user isn’t logged in
+Whenether to show the instance’s specific panel
+When a message has a subject (aka Content Warning), collapse it by default
+Copy the scope (private/unlisted/public) in replies to posts by default
+Allows changing the default behaviour of subject lines in replies
+When set to false, auto-hide the subject field when it's empty
+Hide notices statistics(repeats, favorites, …)
+Hide profile statistics(posts, posts per day, followers, followings, …)
+Which theme to use
+or
+URL of the background, unless viewing a user profile with a background that is set
+or
+URL of the logo
+Whether to use only the logo's shape as a mask (true) or as a regular image (false)
+What margin to use around the logo
+Relative URL which indicates where to redirect when a user is logged in
+Relative URL which indicates where to redirect when a user isn’t logged in
+Whenether to show the instance’s specific panel
+When a message has a subject (aka Content Warning), collapse it by default
+Copy the scope (private/unlisted/public) in replies to posts by default
+Allows changing the default behaviour of subject lines in replies
+When set to false, auto-hide the subject field when it's empty
+Hide notices statistics(repeats, favorites, …)
+Hide profile statistics(posts, posts per day, followers, followings, …)
+An element from mascots - This will be used as the default mascot on MastoFE + (default: :pleroma_fox_tan)
+Location of custom emoji files. * can be used as a wildcard.
+A list of file extensions for emojis, when no emoji.txt for a pack is present.
+Location of the JSON-manifest. This manifest contains information about the emoji-packs you can download. Currently only one manifest can be added (no arrays).
+Enables the gopher interface
+Enables the gopher interface
+Port to bind to
+Port advertised in urls (optional, defaults to port)
+Whether the managed content security policy is enabled
+Whether to additionally send a Strict-Transport-Security header
+The maximum age for the Strict-Transport-Security header if sent
+The maximum age for the Expect-CT header if sent
+The referrer policy to use
+Adds the specified url to report-uri and report-to group in CSP header
+You may want this pool max_connections to be at least equal to the number of federator jobs + retry queue jobs.
+For the federation jobs
+For rich media, media proxy
+For uploaded media (if using a remote uploader and proxy_remote: true)
+The instance’s name
+Email used to reach an Administrator/Moderator of the instance
+Email used for notifications
+The instance’s description, can be seen in nodeinfo and /api/v1/instance
+Posts character limit (CW/Subject included in the counter)
+Hard character limit beyond which remote posts will be dropped
+File size limit of uploads (except for avatar, background, banner)
+File size limit of user’s profile avatars
+File size limit of user’s profile backgrounds
+File size limit of user’s profile banners
+Maximum number of options
+Maximum number of characters per option
+Minimum expiration time
+Maximum expiration time
+Enable registrations for anyone, invitations can be enabled when false
+Enable user invitations for admins (depends on registrations_open: false).
+Require users to confirm their emails before signing in
+Enable federation with other instances
+Max. depth of reply-to activities fetching on incoming federation, to prevent out-of-memory situations while fetching very long threads. Lower this value if you experience out-of-memory crashes.
+Timeout (in days) of each external federation target being unreachable prior to pausing federating to it
+Enable Pleroma’s Relay, which makes it possible to follow a whole instance
+{{ getRewritePolicyExpl(item) }}
+Makes the client API in authentificated mode-only except for user-profiles. Useful for disabling the Local Timeline and The Whole Known Network
+List of ActivityPub instances where private (DMs, followers-only) activities will not be send
+Whenether the config for pleroma-fe is configured in this config or in static/config.json
+MIME-type list of formats allowed to be posted (transformed into HTML)
+Make the content of your Message Rewrite Facility settings public (via nodeinfo)
+Copy the scope (private/unlisted/public) in replies to posts by default
+Allows changing the default behaviour of subject lines in replies
+When set to false, auto-hide the subject field when it's empty
+Set to true to use extended local nicknames format (allows underscores/dashes). This will break federation with older software for theses nicknames
+The maximum number of pinned statuses. '0' will disable the feature
+Set to nicknames of (local) users that every new user should automatically follow
+Set to true to disable automatically adding attachment link text to statuses
+A message that will be send to a newly registered users as a direct message
+The nickname of the local user that sends the welcome message
+The maximum size of the report comment
+If set to true, only mentions at the beginning of a post will be used to address people in direct messages. This is to prevent accidental mentioning of people when talking about them
+If set to true, system data will be shown on /api/pleroma/healthcheck
+The default amount of days to retain remote posts when pruning the database.
+Skip filter out broken threads.
+Allow transferring configuration to DB with the subsequent customization from Admin API
+Enabling following/followers counters synchronization for external users.
+List of the scheme part that is considered valid to be an URL
+Allows to set a token that can be used to authenticate with the admin api without using an actual user by giving it as the admin_token parameter.
+The number of scheduled activities a user is allowed to create in a single day (Default: 25)
+The number of scheduled activities a user is allowed to create in total (Default: 300)
+Whether scheduled activities are sent to the job queue to be executed
+If enabled, when a new user is federated with, fetch some of their latest posts
+The amount of pages to fetch
+If set to true, failed federation jobs will be retried
+The maximum amount of parallel federation jobs running at the same time.
+The initial timeout in seconds
+The maximum number of times a federation job is retried
+List of instances to remove medias from
+The level to be logged by this backend. Note that messages are filtered by the general + :level configuration for the :logger application first.
+The format message used to print logs.
+The device to log error messages to. Defaults to :user + but can be changed to something else such as :standard_error
+Maximum events to buffer while waiting for a confirmation from the IO device (default: 32). Once the buffer is full, the backend will block until a confirmation is received.
+Defaults to: :cyan
+Defaults to: :normal
+Defaults to: :yellow
+Defaults to: :red
+Logging level. It defaults to :info.
+The format message used to print logs.
+Formatter that will be used to format the log. It default to Logger.Formatter
+A string that’s prepended to every message, and is typically set to the app name. It defaults to Elixir
+Syslog facility to be used. It defaults to :local0
+Syslog option to be used. It defaults to :ndelay.
+Logging level. It defaults to :info.
+List of instances to remove medias from
+List of instances to put medias as NSFW (sensitive)
+List of instances to remove from Federated (aka The Whole Known Network) Timeline
+List of instances to reject any activities from
+List of instances to accept any activities from
+List of instances to reject reports from
+List of instances to strip avatars from
+List of instances to strip banners from
+Number of mentioned users after which the message gets delisted + (the message can still be seen, but it will not show up in public timelines and mentioned users won't get notifications about it). + Set to 0 to disable.
+Number of mentioned users after which the messaged gets rejected. Set to 0 to disable.
+A list of patterns which result in message being rejected
+A list of patterns which result in message being removed from federated timelines (a.k.a unlisted)
+Matches a series of regular expressions against the actor field.
+A list of actors, for which to drop any posts mentioning.
+The keys in this section are the domain names that the policy should apply to. Each key should be assigned a list of users that should be allowed through by their ActivityPub ID.
+Allows to enable or disable sending emails. Defaults to false.
+E. g. /usr/bin/sendmail"
+E. g. -N delay,failure,success
+E. g. smtp.avengers.com
+E.g. :always
+E.g. :always
+Enables proxying of remote media to the instance’s proxy
+The base URL to access a user-uploaded file. Useful when you want to proxy the media files via another host/CDN fronts.
+Redirects the client to the real remote URL if there's any HTTP errors. Any error during body processing will not be redirected as the response is chunked
+Limits the content length to be approximately the specified length
+The total time the connection is allowed to read from the remote upstream
+Will not alter content-disposition (up to the upstream)
+Will add content-disposition: attachment to any request
++ Will forward the client's user-agent to the upstream. This may be useful if the upstream is + doing content transformation (encoding, …) depending on the request. +
+resp_headers additional headers
+{{ getPoolExpl(http.pool) }}
+List of domains to bypass the mediaproxy
+A list of metadata providers to enable.
+If set to true nsfw attachments will be shown in previews.
+If enabled the instance will parse metadata from attached links to generate link previews.
+List of hosts which will be ignored by the metadata parser.
+List TLDs (top-level domains) which will ignore for parse metadata. + Default is ["local", "localdomain", "lan"]
+List of Rich Media parsers
+When enabled Pleroma will add a name parameter to the url of the upload, for example + https://instance.tld/media/corndog.png?name=corndog.png
+The base URL to access a user-uploaded file. Useful when you want to proxy the media files via another host
+If you're using a remote uploader, Pleroma will proxy media requests instead of redirecting to it
+Redirects the client to the real remote URL if there's any HTTP errors. + Any error during body processing will not be redirected as the response is chunked
+Limits the content length to be approximately the specified length
+The total time the connection is allowed to read from the remote upstream
+Will not alter content-disposition (up to the upstream)
+Will add content-disposition: attachment to any request
++ Will forward the client's user-agent to the upstream. This may be useful if the upstream is + doing content transformation (encoding, …) depending on the request. +
+resp_headers additional headers
+{{ getPoolExpl(http.pool) }}
+Which directory to store the user-uploads in, relative to pleroma’s working directory
+Text to replace filenames in links. If empty, {random}.extension will be used
+S3 bucket name
+S3 endpoint that the user finally accesses
+If you use S3 compatible service such as Digital Ocean Spaces or CDN, set folder name or "" etc. + For example, when using CDN to S3 virtual host format, set "". + At this time, write CNAME to CDN in public_endpoint. +
+A mailto link for the administrative contact. It’s best if this email is not a personal email address, + but rather a group email so that if a person leaves an organization, is unavailable for an extended period, + or otherwise can’t respond, someone else on the list can.
+VAPID public key
+VAPID private key
+