logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma git clone https://hacktivis.me/git/pleroma.git

cheatsheet.md (60130B)

    

  1. # Configuration Cheat Sheet
  3. This is a cheat sheet for Pleroma configuration file, any setting possible to configure should be listed here.
  5. For OTP installations the configuration is typically stored in `/etc/pleroma/config.exs`.
  7. For from source installations Pleroma configuration works by first importing the base config `config/config.exs`, then overriding it by the environment config `config/$MIX_ENV.exs` and then overriding it by user config `config/$MIX_ENV.secret.exs`. In from source installations you should always make the changes to the user config and NEVER to the base config to avoid breakages and merge conflicts. So for production you change/add configuration to `config/prod.secret.exs`.
  9. To add configuration to your config file, you can copy it from the base config. The latest version of it can be viewed [here](https://git.pleroma.social/pleroma/pleroma/blob/develop/config/config.exs). You can also use this file if you don't know how an option is supposed to be formatted.
  11. ## :shout
  13. * `enabled` - Enables the backend Shoutbox chat feature. Defaults to `true`.
  14. * `limit` - Shout character limit. Defaults to `5_000`
  16. ## :instance
  17. * `name`: The instance’s name.
  18. * `email`: Email used to reach an Administrator/Moderator of the instance.
  19. * `notify_email`: Email used for notifications.
  20. * `description`: The instance’s description, can be seen in nodeinfo and ``/api/v1/instance``.
  21. * `short_description`: Shorter version of instance description, can be seen on ``/api/v1/instance``.
  22. * `limit`: Posts character limit (CW/Subject included in the counter).
  23. * `description_limit`: The character limit for image descriptions.
  24. * `remote_limit`: Hard character limit beyond which remote posts will be dropped.
  25. * `upload_limit`: File size limit of uploads (except for avatar, background, banner).
  26. * `avatar_upload_limit`: File size limit of user’s profile avatars.
  27. * `background_upload_limit`: File size limit of user’s profile backgrounds.
  28. * `banner_upload_limit`: File size limit of user’s profile banners.
  29. * `poll_limits`: A map with poll limits for **local** polls.
  30.     * `max_options`: Maximum number of options.
  31.     * `max_option_chars`: Maximum number of characters per option.
  32.     * `min_expiration`: Minimum expiration time (in seconds).
  33.     * `max_expiration`: Maximum expiration time (in seconds).
  34. * `registrations_open`: Enable registrations for anyone, invitations can be enabled when false.
  35. * `invites_enabled`: Enable user invitations for admins (depends on `registrations_open: false`).
  36. * `account_activation_required`: Require users to confirm their emails before signing in.
  37. * `account_approval_required`: Require users to be manually approved by an admin before signing in.
  38. * `federating`: Enable federation with other instances.
  39. * `federation_incoming_replies_max_depth`: Max. depth of reply-to activities fetching on incoming federation, to prevent out-of-memory situations while fetching very long threads. If set to `nil`, threads of any depth will be fetched. Lower this value if you experience out-of-memory crashes.
  40. * `federation_reachability_timeout_days`: Timeout (in days) of each external federation target being unreachable prior to pausing federating to it.
  41. * `allow_relay`: Permits remote instances to subscribe to all public posts of your instance. This may increase the visibility of your instance.
  42. * `public`: Makes the client API in authenticated mode-only except for user-profiles. Useful for disabling the Local Timeline and The Whole Known Network. Note that there is a dependent setting restricting or allowing unauthenticated access to specific resources, see `restrict_unauthenticated` for more details.
  43. * `quarantined_instances`: ActivityPub instances where private (DMs, followers-only) activities will not be send.
  44. * `allowed_post_formats`: MIME-type list of formats allowed to be posted (transformed into HTML).
  45. * `extended_nickname_format`: Set to `true` to use extended local nicknames format (allows underscores/dashes). This will break federation with
  46.     older software for theses nicknames.
  47. * `max_pinned_statuses`: The maximum number of pinned statuses. `0` will disable the feature.
  48. * `autofollowed_nicknames`: Set to nicknames of (local) users that every new user should automatically follow.
  49. * `autofollowing_nicknames`: Set to nicknames of (local) users that automatically follows every newly registered user.
  50. * `attachment_links`: Set to true to enable automatically adding attachment link text to statuses.
  51. * `max_report_comment_size`: The maximum size of the report comment (Default: `1000`).
  52. * `report_strip_status`: Strip associated statuses in reports to ids when closed/resolved, otherwise keep a copy.
  53. * `safe_dm_mentions`: 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 (e.g. "@friend hey i really don't like @enemy"). Default: `false`.
  54. * `healthcheck`: If set to true, system data will be shown on ``/api/v1/pleroma/healthcheck``.
  55. * `remote_post_retention_days`: The default amount of days to retain remote posts when pruning the database.
  56. * `user_bio_length`: A user bio maximum length (default: `5000`).
  57. * `user_name_length`: A user name maximum length (default: `100`).
  58. * `skip_thread_containment`: Skip filter out broken threads. The default is `false`.
  59. * `limit_to_local_content`: Limit unauthenticated users to search for local statutes and users only. Possible values: `:unauthenticated`, `:all` and `false`. The default is `:unauthenticated`.
  60. * `max_account_fields`: The maximum number of custom fields in the user profile (default: `10`).
  61. * `max_remote_account_fields`: The maximum number of custom fields in the remote user profile (default: `20`).
  62. * `account_field_name_length`: An account field name maximum length (default: `512`).
  63. * `account_field_value_length`: An account field value maximum length (default: `2048`).
  64. * `registration_reason_length`: Maximum registration reason length (default: `500`).
  65. * `external_user_synchronization`: Enabling following/followers counters synchronization for external users.
  66. * `cleanup_attachments`: Remove attachments along with statuses. Does not affect duplicate files and attachments without status. Enabling this will increase load to database when deleting statuses on larger instances.
  67. * `show_reactions`: Let favourites and emoji reactions be viewed through the API (default: `true`).
  68. * `password_reset_token_validity`: The time after which reset tokens aren't accepted anymore, in seconds (default: one day).
  69. * `admin_privileges`: A list of privileges an admin has (e.g. delete messages, manage reports...)
  70.     * Possible values are:
  71.       * `:users_read`
  72.         * Allows admins to fetch users through the admin API.
  73.       * `:users_manage_invites`
  74.         * Allows admins to manage invites. This includes sending, resending, revoking and approving invites.
  75.       * `:users_manage_activation_state`
  76.         * Allows admins to activate and deactivate accounts. This also allows them to see deactivated users through the Mastodon API.
  77.       * `:users_manage_tags`
  78.         * Allows admins to set and remove tags for users. This can be useful in combination with MRF policies, such as `Pleroma.Web.ActivityPub.MRF.TagPolicy`.
  79.       * `:users_manage_credentials`
  80.         * Allows admins to trigger a password reset and set new credentials for an user.
  81.       * `:users_delete`
  82.         * Allows admins to delete accounts. Note that deleting an account is actually deactivating it and removing all data like posts, profile information, etc.
  83.       * `:messages_read`
  84.         * Allows admins to read messages through the admin API, including non-public posts and chats.
  85.       * `:messages_delete`
  86.         * Allows admins to delete messages from other users.
  87.       * `:instances_delete,`
  88.         * Allows admins to remove a whole remote instance from your instance. This will delete all users and messages from that remote instance.
  89.       * `:reports_manage_reports`
  90.         * Allows admins to see and manage reports.
  91.       * `:moderation_log_read,`
  92.         * Allows admins to read the entries in the moderation log.
  93.       * `:emoji_manage_emoji`
  94.         * Allows admins to manage custom emoji on the instance.
  95.       * `:statistics_read,`
  96.         * Allows admins to see some simple statistics about the instance.
  97. * `moderator_privileges`: A list of privileges a moderator has (e.g. delete messages, manage reports...)
  98.     * Possible values are the same as for `admin_privileges`
  100. ## :database
  101. * `improved_hashtag_timeline`: Setting to force toggle / force disable improved hashtags timeline. `:enabled` forces hashtags to be fetched from `hashtags` table for hashtags timeline. `:disabled` forces object-embedded hashtags to be used (slower). Keep it `:auto` for automatic behaviour (it is auto-set to `:enabled` [unless overridden] when HashtagsTableMigrator completes).
  103. ## Background migrations
  104. * `populate_hashtags_table/sleep_interval_ms`: Sleep interval between each chunk of processed records in order to decrease the load on the system (defaults to 0 and should be keep default on most instances).
  105. * `populate_hashtags_table/fault_rate_allowance`: Max rate of failed objects to actually processed objects in order to enable the feature (any value from 0.0 which tolerates no errors to 1.0 which will enable the feature even if hashtags transfer failed for all records).
  107. ## Welcome
  108. * `direct_message`: - welcome message sent as a direct message.
  109.   * `enabled`: Enables the send a direct message to a newly registered user. Defaults to `false`.
  110.   * `sender_nickname`: The nickname of the local user that sends the welcome message.
  111.   * `message`: A message that will be send to a newly registered users as a direct message.
  112. * `chat_message`: - welcome message sent as a chat message.
  113.   * `enabled`: Enables the send a chat message to a newly registered user. Defaults to `false`.
  114.   * `sender_nickname`: The nickname of the local user that sends the welcome message.
  115.   * `message`: A message that will be send to a newly registered users as a chat message.
  116. * `email`: - welcome message sent as a email.
  117.   * `enabled`: Enables the send a welcome email to a newly registered user. Defaults to `false`.
  118.   * `sender`: The email address or tuple with `{nickname, email}` that will use as sender to the welcome email.
  119.   * `subject`: A subject of welcome email.
  120.   * `html`: A html that will be send to a newly registered users as a email.
  121.   * `text`: A text that will be send to a newly registered users as a email.
  123.     Example:
  125.   ```elixir
  126.   config :pleroma, :welcome,
  127.       direct_message: [
  128.         enabled: true,
  129.         sender_nickname: "lain",
  130.         message: "Hi! Welcome on board!"
  131.         ],
  132.       email: [
  133.         enabled: true,
  134.         sender: {"Pleroma App", "welcome@pleroma.app"},
  135.         subject: "Welcome to <%= instance_name %>",
  136.         html: "Welcome to <%= instance_name %>",
  137.         text: "Welcome to <%= instance_name %>"
  138.     ]
  139.   ```
  141. ## Message rewrite facility
  143. ### :mrf
  144. * `policies`: Message Rewrite Policy, either one or a list. Here are the ones available by default:
  145.     * `Pleroma.Web.ActivityPub.MRF.NoOpPolicy`: Doesn’t modify activities (default).
  146.     * `Pleroma.Web.ActivityPub.MRF.DropPolicy`: Drops all activities. It generally doesn’t makes sense to use in production.
  147.     * `Pleroma.Web.ActivityPub.MRF.SimplePolicy`: Restrict the visibility of activities from certains instances (See [`:mrf_simple`](#mrf_simple)).
  148.     * `Pleroma.Web.ActivityPub.MRF.TagPolicy`: Applies policies to individual users based on tags, which can be set using pleroma-fe/admin-fe/any other app that supports Pleroma Admin API. For example it allows marking posts from individual users nsfw (sensitive).
  149.     * `Pleroma.Web.ActivityPub.MRF.SubchainPolicy`: Selectively runs other MRF policies when messages match (See [`:mrf_subchain`](#mrf_subchain)).
  150.     * `Pleroma.Web.ActivityPub.MRF.RejectNonPublic`: Drops posts with non-public visibility settings (See [`:mrf_rejectnonpublic`](#mrf_rejectnonpublic)).
  151.     * `Pleroma.Web.ActivityPub.MRF.EnsureRePrepended`: Rewrites posts to ensure that replies to posts with subjects do not have an identical subject and instead begin with re:.
  152.     * `Pleroma.Web.ActivityPub.MRF.AntiLinkSpamPolicy`: Rejects posts from likely spambots by rejecting posts from new users that contain links.
  153.     * `Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy`: Crawls attachments using their MediaProxy URLs so that the MediaProxy cache is primed.
  154.     * `Pleroma.Web.ActivityPub.MRF.MentionPolicy`: Drops posts mentioning configurable users. (See [`:mrf_mention`](#mrf_mention)).
  155.     * `Pleroma.Web.ActivityPub.MRF.VocabularyPolicy`: Restricts activities to a configured set of vocabulary. (See [`:mrf_vocabulary`](#mrf_vocabulary)).
  156.     * `Pleroma.Web.ActivityPub.MRF.ObjectAgePolicy`: Rejects or delists posts based on their age when received. (See [`:mrf_object_age`](#mrf_object_age)).
  157.     * `Pleroma.Web.ActivityPub.MRF.ActivityExpirationPolicy`: Sets a default expiration on all posts made by users of the local instance. Requires `Pleroma.Workers.PurgeExpiredActivity` to be enabled for processing the scheduled deletions.
  158.     * `Pleroma.Web.ActivityPub.MRF.ForceBotUnlistedPolicy`: Makes all bot posts to disappear from public timelines.
  159.     * `Pleroma.Web.ActivityPub.MRF.FollowBotPolicy`: Automatically follows newly discovered users from the specified bot account. Local accounts, locked accounts, and users with "#nobot" in their bio are respected and excluded from being followed.
  160.     * `Pleroma.Web.ActivityPub.MRF.AntiFollowbotPolicy`: Drops follow requests from followbots. Users can still allow bots to follow them by first following the bot.
  161.     * `Pleroma.Web.ActivityPub.MRF.KeywordPolicy`: Rejects or removes from the federated timeline or replaces keywords. (See [`:mrf_keyword`](#mrf_keyword)).
  162.     * `Pleroma.Web.ActivityPub.MRF.ForceMentionsInContent`: Forces every mentioned user to be reflected in the post content.
  163.     * `Pleroma.Web.ActivityPub.MRF.InlineQuotePolicy`: Forces quote post URLs to be reflected in the message content inline.
  164.     * `Pleroma.Web.ActivityPub.MRF.QuoteToLinkTagPolicy`: Force a Link tag for posts quoting another post. (may break outgoing federation of quote posts with older Pleroma versions)
  165. * `transparency`: Make the content of your Message Rewrite Facility settings public (via nodeinfo).
  166. * `transparency_exclusions`: Exclude specific instance names from MRF transparency.  The use of the exclusions feature will be disclosed in nodeinfo as a boolean value.
  168. ## Federation
  169. ### MRF policies
  171. !!! note
  172.     Configuring MRF policies is not enough for them to take effect. You have to enable them by specifying their module in `policies` under [:mrf](#mrf) section.
  174. #### :mrf_simple
  175. * `media_removal`: List of instances to strip media attachments from and the reason for doing so.
  176. * `media_nsfw`: List of instances to tag all media as NSFW (sensitive) from and the reason for doing so.
  177. * `federated_timeline_removal`: List of instances to remove from the Federated Timeline (aka The Whole Known Network) and the reason for doing so.
  178. * `reject`: List of instances to reject activities (except deletes) from and the reason for doing so.
  179. * `accept`: List of instances to only accept activities (except deletes) from and the reason for doing so.
  180. * `followers_only`: Force posts from the given instances to be visible by followers only and the reason for doing so.
  181. * `report_removal`: List of instances to reject reports from and the reason for doing so.
  182. * `avatar_removal`: List of instances to strip avatars from and the reason for doing so.
  183. * `banner_removal`: List of instances to strip banners from and the reason for doing so.
  184. * `reject_deletes`: List of instances to reject deletions from and the reason for doing so.
  186. #### :mrf_subchain
  187. This policy processes messages through an alternate pipeline when a given message matches certain criteria.
  188. All criteria are configured as a map of regular expressions to lists of policy modules.
  190. * `match_actor`: Matches a series of regular expressions against the actor field.
  192. Example:
  194. ```elixir
  195. config :pleroma, :mrf_subchain,
  196.   match_actor: %{
  197.     ~r/https:\/\/example.com/s => [Pleroma.Web.ActivityPub.MRF.DropPolicy]
  198.   }
  199. ```
  201. #### :mrf_rejectnonpublic
  202. * `allow_followersonly`: whether to allow followers-only posts.
  203. * `allow_direct`: whether to allow direct messages.
  205. #### :mrf_hellthread
  206. * `delist_threshold`: 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.
  207. * `reject_threshold`: Number of mentioned users after which the messaged gets rejected. Set to 0 to disable.
  209. #### :mrf_keyword
  210. * `reject`: A list of patterns which result in message being rejected, each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  211. * `federated_timeline_removal`: A list of patterns which result in message being removed from federated timelines (a.k.a unlisted), each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  212. * `replace`: A list of tuples containing `{pattern, replacement}`, `pattern` can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  214. #### :mrf_mention
  215. * `actors`: A list of actors, for which to drop any posts mentioning.
  217. #### :mrf_vocabulary
  218. * `accept`: A list of ActivityStreams terms to accept.  If empty, all supported messages are accepted.
  219. * `reject`: A list of ActivityStreams terms to reject.  If empty, no messages are rejected.
  221. #### :mrf_user_allowlist
  223. The keys in this section are the domain names that the policy should apply to.
  224. Each key should be assigned a list of users that should be allowed through by
  225. their ActivityPub ID.
  227. An example:
  229. ```elixir
  230. config :pleroma, :mrf_user_allowlist, %{
  231.   "example.org" => ["https://example.org/users/admin"]
  232. }
  233. ```
  235. #### :mrf_object_age
  236. * `threshold`: Required time offset (in seconds) compared to your server clock of an incoming post before actions are taken.
  237.   e.g., A value of 900 results in any post with a timestamp older than 15 minutes will be acted upon.
  238. * `actions`: A list of actions to apply to the post:
  239.   * `:delist` removes the post from public timelines
  240.   * `:strip_followers` removes followers from the ActivityPub recipient list, ensuring they won't be delivered to home timelines, additionally for followers-only it degrades to a direct message
  241.   * `:reject` rejects the message entirely
  243. #### :mrf_steal_emoji
  244. * `hosts`: List of hosts to steal emojis from
  245. * `rejected_shortcodes`: Regex-list of shortcodes to reject
  246. * `size_limit`: File size limit (in bytes), checked before an emoji is saved to the disk
  248. #### :mrf_activity_expiration
  250. * `days`: Default global expiration time for all local Create activities (in days)
  252. #### :mrf_hashtag
  254. * `sensitive`: List of hashtags to mark activities as sensitive (default: `nsfw`)
  255. * `federated_timeline_removal`: List of hashtags to remove activities from the federated timeline (aka TWNK)
  256. * `reject`: List of hashtags to reject activities from
  258. Notes:
  259. - The hashtags in the configuration do not have a leading `#`.
  260. - This MRF Policy is always enabled, if you want to disable it you have to set empty lists
  262. #### :mrf_follow_bot
  264. * `follower_nickname`: The name of the bot account to use for following newly discovered users. Using `followbot` or similar is strongly suggested.
  266. #### :mrf_emoji
  267. * `remove_url`: A list of patterns which result in emoji whose URL matches being removed from the message. This will apply to statuses, emoji reactions, and user profiles. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  268. * `remove_shortcode`: A list of patterns which result in emoji whose shortcode matches being removed from the message. This will apply to statuses, emoji reactions, and user profiles. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  269. * `federated_timeline_removal_url`: A list of patterns which result in message with emojis whose URLs match being removed from federated timelines (a.k.a unlisted). This will apply only to statuses. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  270. * `federated_timeline_removal_shortcode`: A list of patterns which result in message with emojis whose shortcodes match being removed from federated timelines (a.k.a unlisted). This will apply only to statuses. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
  272. #### :mrf_inline_quote
  273. * `template`: The template to append to the post. `{url}` will be replaced with the actual link to the quoted post. Default: `<bdi>RT:</bdi> {url}`
  275. ### :activitypub
  276. * `unfollow_blocked`: Whether blocks result in people getting unfollowed
  277. * `outgoing_blocks`: Whether to federate blocks to other instances
  278. * `blockers_visible`: Whether a user can see the posts of users who blocked them
  279. * `deny_follow_blocked`: Whether to disallow following an account that has blocked the user in question
  280. * `sign_object_fetches`: Sign object fetches with HTTP signatures
  281. * `authorized_fetch_mode`: Require HTTP signatures for AP fetches
  283. ## Pleroma.User
  285. * `restricted_nicknames`: List of nicknames users may not register with.
  286. * `email_blacklist`: List of email domains users may not register with.
  288. ## Pleroma.ScheduledActivity
  290. * `daily_user_limit`: the number of scheduled activities a user is allowed to create in a single day (Default: `25`)
  291. * `total_user_limit`: the number of scheduled activities a user is allowed to create in total (Default: `300`)
  292. * `enabled`: whether scheduled activities are sent to the job queue to be executed
  294. ### :frontend_configurations
  296. This can be used to configure a keyword list that keeps the configuration data for any kind of frontend. By default, settings for `pleroma_fe` are configured. You can find the documentation for `pleroma_fe` configuration into [Pleroma-FE configuration and customization for instance administrators](/frontend/CONFIGURATION/#options).
  298. Frontends can access these settings at `/api/v1/pleroma/frontend_configurations`
  300. To add your own configuration for PleromaFE, use it like this:
  302. ```elixir
  303. config :pleroma, :frontend_configurations,
  304.   pleroma_fe: %{
  305.     theme: "pleroma-dark",
  306.     # ... see /priv/static/static/config.json for the available keys.
  307. }
  308. ```
  310. These settings **need to be complete**, they will override the defaults.
  312. ### :static_fe
  314. Render profiles and posts using server-generated HTML that is viewable without using JavaScript.
  316. Available options:
  318. * `enabled` - Enables the rendering of static HTML. Defaults to `false`.
  320. ### :assets
  322. This section configures assets to be used with various frontends. Currently the only option
  323. relates to mascots on the mastodon frontend
  325. * `mascots`: KeywordList of mascots, each element __MUST__ contain both a `url` and a
  326.   `mime_type` key.
  327. * `default_mascot`: An element from `mascots` - This will be used as the default mascot
  328.   on MastoFE (default: `:pleroma_fox_tan`).
  330. ### :manifest
  332. This section describe PWA manifest instance-specific values. Currently this option relate only for MastoFE.
  334. * `icons`: Describe the icons of the app, this a list of maps describing icons in the same way as the
  335.   [spec](https://www.w3.org/TR/appmanifest/#imageresource-and-its-members) describes it.
  337.   Example:
  339.   ```elixir
  340.   config :pleroma, :manifest,
  341.     icons: [
  342.       %{
  343.         src: "/static/logo.png"
  344.       },
  345.       %{
  346.         src: "/static/icon.png",
  347.         type: "image/png"
  348.       },
  349.       %{
  350.         src: "/static/icon.ico",
  351.         sizes: "72x72 96x96 128x128 256x256"
  352.       }
  353.     ]
  354.   ```
  356. * `theme_color`: Describe the theme color of the app. (Example: `"#282c37"`, `"rebeccapurple"`).
  357. * `background_color`: Describe the background color of the app. (Example: `"#191b22"`, `"aliceblue"`).
  359. ## :emoji
  361. * `shortcode_globs`: Location of custom emoji files. `*` can be used as a wildcard. Example `["/emoji/custom/**/*.png"]`
  362. * `pack_extensions`: A list of file extensions for emojis, when no emoji.txt for a pack is present. Example `[".png", ".gif"]`
  363. * `groups`: Emojis are ordered in groups (tags). This is an array of key-value pairs where the key is the groupname and the value the location or array of locations. `*` can be used as a wildcard. Example `[Custom: ["/emoji/*.png", "/emoji/custom/*.png"]]`
  364. * `default_manifest`: 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).
  365. * `shared_pack_cache_seconds_per_file`: When an emoji pack is shared, the archive is created and cached in
  366.   memory for this amount of seconds multiplied by the number of files.
  368. ## :media_proxy
  370. * `enabled`: Enables proxying of remote media to the instance’s proxy
  371. * `base_url`: The base URL to access a user-uploaded file. Useful when you want to proxy the media files via another host/CDN fronts.
  372. * `proxy_opts`: All options defined in `Pleroma.ReverseProxy` documentation, defaults to `[max_body_length: (25*1_048_576)]`.
  373. * `whitelist`: List of hosts with scheme to bypass the mediaproxy (e.g. `https://example.com`)
  374. * `invalidation`: options for remove media from cache after delete object:
  375.   * `enabled`: Enables purge cache
  376.   * `provider`: Which one of  the [purge cache strategy](#purge-cache-strategy) to use.
  378. ## :media_preview_proxy
  380. * `enabled`: Enables proxying of remote media preview to the instance’s proxy. Requires enabled media proxy (`media_proxy/enabled`).
  381. * `thumbnail_max_width`: Max width of preview thumbnail for images (video preview always has original dimensions).
  382. * `thumbnail_max_height`: Max height of preview thumbnail for images (video preview always has original dimensions).
  383. * `image_quality`: Quality of the output. Ranges from 0 (min quality) to 100 (max quality).
  384. * `min_content_length`: Min content length to perform preview, in bytes. If greater than 0, media smaller in size will be served as is, without thumbnailing.
  386. ### Purge cache strategy
  388. #### Pleroma.Web.MediaProxy.Invalidation.Script
  390. This strategy allow perform external shell script to purge cache.
  391. Urls of attachments are passed to the script as arguments.
  393. * `script_path`: Path to the external script.
  394. * `url_format`: Set to `:htcacheclean` if using Apache's htcacheclean utility.
  396. Example:
  398. ```elixir
  399. config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Script,
  400.   script_path: "./installation/nginx-cache-purge.example"
  401. ```
  403. #### Pleroma.Web.MediaProxy.Invalidation.Http
  405. This strategy allow perform custom http request to purge cache.
  407. * `method`: http method. default is `purge`
  408. * `headers`: http headers.
  409. * `options`: request options.
  411. Example:
  412. ```elixir
  413. config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Http,
  414.   method: :purge,
  415.   headers: [],
  416.   options: []
  417. ```
  419. ## Link previews
  421. ### Pleroma.Web.Metadata (provider)
  422. * `providers`: a list of metadata providers to enable. Providers available:
  423.     * `Pleroma.Web.Metadata.Providers.OpenGraph`
  424.     * `Pleroma.Web.Metadata.Providers.TwitterCard`
  425. * `unfurl_nsfw`: If set to `true` nsfw attachments will be shown in previews.
  427. ### :rich_media (consumer)
  428. * `enabled`: if enabled the instance will parse metadata from attached links to generate link previews.
  429. * `ignore_hosts`: list of hosts which will be ignored by the metadata parser. For example `["accounts.google.com", "xss.website"]`, defaults to `[]`.
  430. * `ignore_tld`: list TLDs (top-level domains) which will ignore for parse metadata. default is ["local", "localdomain", "lan"].
  431. * `parsers`: list of Rich Media parsers.
  432. * `failure_backoff`: Amount of milliseconds after request failure, during which the request will not be retried.
  434. ## HTTP server
  436. ### Pleroma.Web.Endpoint
  438. !!! note
  439.     `Phoenix` endpoint configuration, all configuration options can be viewed [here](https://hexdocs.pm/phoenix/Phoenix.Endpoint.html#module-dynamic-configuration), only common options are listed here.
  441. * `http` - a list containing http protocol configuration, all configuration options can be viewed [here](https://hexdocs.pm/plug_cowboy/Plug.Cowboy.html#module-options), only common options are listed here. For deployment using docker, you need to set this to `[ip: {0,0,0,0}, port: 4000]` to make pleroma accessible from other containers (such as your nginx server).
  442.   - `ip` - a tuple consisting of 4 integers
  443.   - `port`
  444. * `url` - a list containing the configuration for generating urls, accepts
  445.   - `host` - the host without the scheme and a post (e.g `example.com`, not `https://example.com:2020`)
  446.   - `scheme` - e.g `http`, `https`
  447.   - `port`
  448.   - `path`
  449. * `extra_cookie_attrs` - a list of `Key=Value` strings to be added as non-standard cookie attributes. Defaults to `["SameSite=Lax"]`. See the [SameSite article](https://www.owasp.org/index.php/SameSite) on OWASP for more info.
  451. Example:
  452. ```elixir
  453. config :pleroma, Pleroma.Web.Endpoint,
  454.   url: [host: "example.com", port: 2020, scheme: "https"],
  455.   http: [
  456.     port: 8080,
  457.     ip: {127, 0, 0, 1}
  458.   ]
  459. ```
  461. This will make Pleroma listen on `127.0.0.1` port `8080` and generate urls starting with `https://example.com:2020`
  463. ### :http_security
  464. * ``enabled``: Whether the managed content security policy is enabled.
  465. * ``sts``: Whether to additionally send a `Strict-Transport-Security` header.
  466. * ``sts_max_age``: The maximum age for the `Strict-Transport-Security` header if sent.
  467. * ``ct_max_age``: The maximum age for the `Expect-CT` header if sent.
  468. * ``referrer_policy``: The referrer policy to use, either `"same-origin"` or `"no-referrer"`.
  469. * ``report_uri``: Adds the specified url to `report-uri` and `report-to` group in CSP header.
  471. ### Pleroma.Web.Plugs.RemoteIp
  473. !!! warning
  474.     If your instance is not behind at least one reverse proxy, you should not enable this plug.
  476. `Pleroma.Web.Plugs.RemoteIp` is a shim to call [`RemoteIp`](https://git.pleroma.social/pleroma/remote_ip) but with runtime configuration.
  478. Available options:
  480. * `enabled` - Enable/disable the plug. Defaults to `false`.
  481. * `headers` - A list of strings naming the HTTP headers to use when deriving the true client IP address. Defaults to `["x-forwarded-for"]`.
  482. * `proxies` - A list of upstream proxy IP subnets in CIDR notation from which we will parse the content of `headers`. Defaults to `[]`. IPv4 entries without a bitmask will be assumed to be /32 and IPv6 /128.
  483. * `reserved` - A list of reserved IP subnets in CIDR notation which should be ignored if found in `headers`. Defaults to `["127.0.0.0/8", "::1/128", "fc00::/7", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]`.
  486. ### :rate_limit
  488. !!! note
  489.    If your instance is behind a reverse proxy ensure [`Pleroma.Web.Plugs.RemoteIp`](#pleroma-plugs-remoteip) is enabled (it is enabled by default).
  491. A keyword list of rate limiters where a key is a limiter name and value is the limiter configuration. The basic configuration is a tuple where:
  493. * The first element: `scale` (Integer). The time scale in milliseconds.
  494. * The second element: `limit` (Integer). How many requests to limit in the time scale provided.
  496. It is also possible to have different limits for unauthenticated and authenticated users: the keyword value must be a list of two tuples where the first one is a config for unauthenticated users and the second one is for authenticated.
  498. For example:
  500. ```elixir
  501. config :pleroma, :rate_limit,
  502.   authentication: {60_000, 15},
  503.   search: [{1000, 10}, {1000, 30}]
  504. ```
  506. Means that:
  508. 1. In 60 seconds, 15 authentication attempts can be performed from the same IP address.
  509. 2. In 1 second, 10 search requests can be performed from the same IP address by unauthenticated users, while authenticated users can perform 30 search requests per second.
  511. Supported rate limiters:
  513. * `:search` - Account/Status search.
  514. * `:timeline` - Timeline requests (each timeline has it's own limiter).
  515. * `:app_account_creation` - Account registration from the API.
  516. * `:relations_actions` - Following/Unfollowing in general.
  517. * `:relation_id_action` - Following/Unfollowing for a specific user.
  518. * `:statuses_actions` - Status actions such as: (un)repeating, (un)favouriting, creating, deleting.
  519. * `:status_id_action` - (un)Repeating/(un)Favouriting a particular status.
  520. * `:authentication` - Authentication actions, i.e getting an OAuth token.
  521. * `:password_reset` - Requesting password reset emails.
  522. * `:account_confirmation_resend` - Requesting resending account confirmation emails.
  523. * `:ap_routes` - Requesting statuses via ActivityPub.
  525. ### :web_cache_ttl
  527. The expiration time for the web responses cache. Values should be in milliseconds or `nil` to disable expiration.
  529. Available caches:
  531. * `:activity_pub` - activity pub routes (except question activities). Defaults to `nil` (no expiration).
  532. * `:activity_pub_question` - activity pub routes (question activities). Defaults to `30_000` (30 seconds).
  534. ## HTTP client
  536. ### :http
  538. * `proxy_url`: an upstream proxy to fetch posts and/or media with, (default: `nil`)
  539. * `send_user_agent`: should we include a user agent with HTTP requests? (default: `true`)
  540. * `user_agent`: what user agent should we use? (default: `:default`), must be string or `:default`
  541. * `adapter`: array of adapter options
  543. ### :hackney_pools
  545. Advanced. Tweaks Hackney (http client) connections pools.
  547. There's three pools used:
  549. * `:federation` for the federation jobs.
  550.   You may want this pool max_connections to be at least equal to the number of federator jobs + retry queue jobs.
  551. * `:media` for rich media, media proxy
  552. * `:upload` for uploaded media (if using a remote uploader and `proxy_remote: true`)
  554. For each pool, the options are:
  556. * `max_connections` - how much connections a pool can hold
  557. * `timeout` - retention duration for connections
  560. ### :connections_pool
  562. *For `gun` adapter*
  564. Settings for HTTP connection pool.
  566. * `:connection_acquisition_wait` - Timeout to acquire a connection from pool.The total max time is this value multiplied by the number of retries.
  567. * `connection_acquisition_retries` - Number of attempts to acquire the connection from the pool if it is overloaded. Each attempt is timed `:connection_acquisition_wait` apart.
  568. * `:max_connections` - Maximum number of connections in the pool.
  569. * `:connect_timeout` - Timeout to connect to the host.
  570. * `:reclaim_multiplier` - Multiplied by `:max_connections` this will be the maximum number of idle connections that will be reclaimed in case the pool is overloaded.
  572. ### :pools
  574. *For `gun` adapter*
  576. Settings for request pools. These pools are limited on top of `:connections_pool`.
  578. There are four pools used:
  580. * `:federation` for the federation jobs. You may want this pool's max_connections to be at least equal to the number of federator jobs + retry queue jobs.
  581. * `:media` - for rich media, media proxy.
  582. * `:upload` - for proxying media when a remote uploader is used and `proxy_remote: true`.
  583. * `:default` - for other requests.
  585. For each pool, the options are:
  587. * `:size` - limit to how much requests can be concurrently executed.
  588. * `:recv_timeout` - timeout while `gun` will wait for response
  589. * `:max_waiting` - limit to how much requests can be waiting for others to finish, after this is reached, subsequent requests will be dropped.
  591. ## Captcha
  593. ### Pleroma.Captcha
  595. * `enabled`: Whether the captcha should be shown on registration.
  596. * `method`: The method/service to use for captcha.
  597. * `seconds_valid`: The time in seconds for which the captcha is valid.
  599. ### Captcha providers
  601. #### Pleroma.Captcha.Native
  603. A built-in captcha provider. Enabled by default.
  605. #### Pleroma.Captcha.Kocaptcha
  607. Kocaptcha is a very simple captcha service with a single API endpoint,
  608. the source code is here: [kocaptcha](https://github.com/koto-bank/kocaptcha). The default endpoint
  609. `https://captcha.kotobank.ch` is hosted by the developer.
  611. * `endpoint`: the Kocaptcha endpoint to use.
  613. ## Uploads
  615. ### Pleroma.Upload
  617. * `uploader`: Which one of the [uploaders](#uploaders) to use.
  618. * `filters`: List of [upload filters](#upload-filters) to use.
  619. * `link_name`: 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`. This is needed to provide the correct filename in Content-Disposition headers when using filters like `Pleroma.Upload.Filter.Dedupe`
  620. * `base_url`: The base URL to access a user-uploaded file. Useful when you want to host the media files via another domain or are using a 3rd party S3 provider.
  621. * `proxy_remote`: If you're using a remote uploader, Pleroma will proxy media requests instead of redirecting to it.
  622. * `proxy_opts`: Proxy options, see `Pleroma.ReverseProxy` documentation.
  623. * `filename_display_max_length`: Set max length of a filename to display. 0 = no limit. Default: 30.
  624. * `default_description`: Sets which default description an image has if none is set explicitly. Options: nil (default) - Don't set a default, :filename - use the filename of the file, a string (e.g. "attachment") - Use this string
  626. !!! warning
  627.     `strip_exif` has been replaced by `Pleroma.Upload.Filter.Mogrify`.
  629. ### Uploaders
  631. #### Pleroma.Uploaders.Local
  633. * `uploads`: Which directory to store the user-uploads in, relative to pleroma’s working directory.
  635. #### Pleroma.Uploaders.S3
  637. Don't forget to configure [Ex AWS S3](#ex-aws-s3-settings)
  639. * `bucket`: S3 bucket name.
  640. * `bucket_namespace`: S3 bucket namespace.
  641. * `truncated_namespace`: If you use S3 compatible service such as Digital Ocean Spaces or CDN, set folder name or "" etc.
  642. * `streaming_enabled`: Enable streaming uploads, when enabled the file will be sent to the server in chunks as it's being read. This may be unsupported by some providers, try disabling this if you have upload problems.
  644. #### Ex AWS S3 settings
  646. * `access_key_id`: Access key ID
  647. * `secret_access_key`: Secret access key
  648. * `host`: S3 host
  650. Example:
  652. ```elixir
  653. config :ex_aws, :s3,
  654.   access_key_id: "xxxxxxxxxx",
  655.   secret_access_key: "yyyyyyyyyy",
  656.   host: "s3.eu-central-1.amazonaws.com"
  657. ```
  659. ### Upload filters
  661. #### Pleroma.Upload.Filter.AnonymizeFilename
  663. This filter replaces the filename (not the path) of an upload. For complete obfuscation, add
  664. `Pleroma.Upload.Filter.Dedupe` before AnonymizeFilename.
  666. * `text`: Text to replace filenames in links. If empty, `{random}.extension` will be used. You can get the original filename extension by using `{extension}`, for example `custom-file-name.{extension}`.
  668. #### Pleroma.Upload.Filter.Dedupe
  670. No specific configuration.
  672. #### Pleroma.Upload.Filter.Exiftool.StripLocation
  674. This filter only strips the GPS and location metadata with Exiftool leaving color profiles and attributes intact.
  676. No specific configuration.
  678. #### Pleroma.Upload.Filter.Exiftool.ReadDescription
  680. This filter reads the ImageDescription and iptc:Caption-Abstract fields with Exiftool so clients can prefill the media description field.
  682. No specific configuration.
  684. #### Pleroma.Upload.Filter.OnlyMedia
  686. This filter rejects uploads that are not identified with Content-Type matching audio/\*, image/\*, or video/\*
  688. No specific configuration.
  690. #### Pleroma.Upload.Filter.Mogrify
  692. * `args`: List of actions for the `mogrify` command like `"strip"` or `["strip", "auto-orient", {"implode", "1"}]`.
  694. ## Email
  696. ### Pleroma.Emails.Mailer
  697. * `adapter`: one of the mail adapters listed in [Swoosh readme](https://github.com/swoosh/swoosh#adapters), or `Swoosh.Adapters.Local` for in-memory mailbox.
  698. * `api_key` / `password` and / or other adapter-specific settings, per the above documentation.
  699. * `enabled`: Allows enable/disable send  emails. Default: `false`.
  701. An example for Sendgrid adapter:
  703. ```elixir
  704. config :pleroma, Pleroma.Emails.Mailer,
  705.   enabled: true,
  706.   adapter: Swoosh.Adapters.Sendgrid,
  707.   api_key: "YOUR_API_KEY"
  708. ```
  710. An example for SMTP adapter:
  712. ```elixir
  713. config :pleroma, Pleroma.Emails.Mailer,
  714.   enabled: true,
  715.   adapter: Swoosh.Adapters.SMTP,
  716.   relay: "smtp.gmail.com",
  717.   username: "YOUR_USERNAME@gmail.com",
  718.   password: "YOUR_SMTP_PASSWORD",
  719.   port: 465,
  720.   ssl: true,
  721.   auth: :always
  722. ```
  724. ### :email_notifications
  726. Email notifications settings.
  728.   - digest - emails of "what you've missed" for users who have been
  729.     inactive for a while.
  730.     - active: globally enable or disable digest emails
  731.     - schedule: When to send digest email, in [crontab format](https://en.wikipedia.org/wiki/Cron).
  732.       "0 0 * * 0" is the default, meaning "once a week at midnight on Sunday morning"
  733.     - interval: Minimum interval between digest emails to one user
  734.     - inactivity_threshold: Minimum user inactivity threshold
  736. ### Pleroma.Emails.UserEmail
  738. - `:logo` - a path to a custom logo. Set it to `nil` to use the default Pleroma logo.
  739. - `:styling` - a map with color settings for email templates.
  741. ### Pleroma.Emails.NewUsersDigestEmail
  743. - `:enabled` - a boolean, enables new users admin digest email when `true`. Defaults to `false`.
  745. ## Background jobs
  747. ### Oban
  749. [Oban](https://github.com/sorentwo/oban) asynchronous job processor configuration.
  751. Configuration options described in [Oban readme](https://github.com/sorentwo/oban#usage):
  753. * `repo` - app's Ecto repo (`Pleroma.Repo`)
  754. * `log` - logs verbosity
  755. * `queues` - job queues (see below)
  756. * `crontab` - periodic jobs, see [`Oban.Cron`](#obancron)
  758. Pleroma has the following queues:
  760. * `activity_expiration` - Activity expiration
  761. * `federator_outgoing` - Outgoing federation
  762. * `federator_incoming` - Incoming federation
  763. * `mailer` - Email sender, see [`Pleroma.Emails.Mailer`](#pleromaemailsmailer)
  764. * `transmogrifier` - Transmogrifier
  765. * `web_push` - Web push notifications
  766. * `scheduled_activities` - Scheduled activities, see [`Pleroma.ScheduledActivity`](#pleromascheduledactivity)
  768. #### Oban.Cron
  770. Pleroma has these periodic job workers:
  772. * `Pleroma.Workers.Cron.DigestEmailsWorker` - digest emails for users with new mentions and follows
  773. * `Pleroma.Workers.Cron.NewUsersDigestWorker` - digest emails for admins with new registrations
  775. ```elixir
  776. config :pleroma, Oban,
  777.   repo: Pleroma.Repo,
  778.   verbose: false,
  779.   prune: {:maxlen, 1500},
  780.   queues: [
  781.     federator_incoming: 50,
  782.     federator_outgoing: 50
  783.   ],
  784.   crontab: [
  785.     {"0 0 * * 0", Pleroma.Workers.Cron.DigestEmailsWorker},
  786.     {"0 0 * * *", Pleroma.Workers.Cron.NewUsersDigestWorker}
  787.   ]
  788. ```
  790. This config contains two queues: `federator_incoming` and `federator_outgoing`. Both have the number of max concurrent jobs set to `50`.
  792. #### Migrating `pleroma_job_queue` settings
  794. `config :pleroma_job_queue, :queues` is replaced by `config :pleroma, Oban, :queues` and uses the same format (keys are queues' names, values are max concurrent jobs numbers).
  796. ### :workers
  798. Includes custom worker options not interpretable directly by `Oban`.
  800. * `retries` — keyword lists where keys are `Oban` queues (see above) and values are numbers of max attempts for failed jobs.
  802. Example:
  804. ```elixir
  805. config :pleroma, :workers,
  806.   retries: [
  807.     federator_incoming: 5,
  808.     federator_outgoing: 5
  809.   ]
  810. ```
  812. #### Migrating `Pleroma.Web.Federator.RetryQueue` settings
  814. * `max_retries` is replaced with `config :pleroma, :workers, retries: [federator_outgoing: 5]`
  815. * `enabled: false` corresponds to `config :pleroma, :workers, retries: [federator_outgoing: 1]`
  816. * deprecated options: `max_jobs`, `initial_timeout`
  818. ## :web_push_encryption, :vapid_details
  820. Web Push Notifications configuration. You can use the mix task `mix web_push.gen.keypair` to generate it.
  822. * ``subject``: 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.
  823. * ``public_key``: VAPID public key
  824. * ``private_key``: VAPID private key
  826. ## :logger
  827. * `backends`: `:console` is used to send logs to stdout, `{ExSyslogger, :ex_syslogger}` to log to syslog
  829. An example to enable ONLY ExSyslogger (f/ex in ``prod.secret.exs``) with info and debug suppressed:
  830. ```elixir
  831. config :logger,
  832.   backends: [{ExSyslogger, :ex_syslogger}]
  834. config :logger, :ex_syslogger,
  835.   level: :warn
  836. ```
  838. Another example, keeping console output and adding the pid to syslog output:
  839. ```elixir
  840. config :logger,
  841.   backends: [:console, {ExSyslogger, :ex_syslogger}]
  843. config :logger, :ex_syslogger,
  844.   level: :warn,
  845.   option: [:pid, :ndelay]
  846. ```
  848. See: [logger’s documentation](https://hexdocs.pm/logger/Logger.html) and [ex_syslogger’s documentation](https://hexdocs.pm/ex_syslogger/)
  850. An example of logging info to local syslog, but debug to console:
  851. ```elixir
  852. config :logger,
  853.   backends: [ {ExSyslogger, :ex_syslogger}, :console ],
  854.   level: :info
  856. config :logger, :ex_syslogger,
  857.   level: :info,
  858.   ident: "pleroma",
  859.   format: "$metadata[$level] $message"
  861. config :logger, :console,
  862.   level: :debug,
  863.   format: "\n$time $metadata[$level] $message\n",
  864.   metadata: [:request_id]
  865. ```
  869. ## Database options
  871. ### RUM indexing for full text search
  873. !!! warning
  874.     It is recommended to use PostgreSQL v11 or newer. We have seen some minor issues with lower PostgreSQL versions.
  876. * `rum_enabled`: If RUM indexes should be used. Defaults to `false`.
  878. 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.
  880. 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.
  882. To enable them, both the `rum_enabled` flag has to be set and the following special migration has to be run:
  884. `mix ecto.migrate --migrations-path priv/repo/optional_migrations/rum_indexing/`
  886. This will probably take a long time.
  888. ## Alternative client protocols
  890. ### BBS / SSH access
  892. This feature has been removed from Pleroma core.
  893. However, a client has been made and is available at https://git.pleroma.social/Duponin/sshocial.
  895. ### :gopher
  896. * `enabled`: Enables the gopher interface
  897. * `ip`: IP address to bind to
  898. * `port`: Port to bind to
  899. * `dstport`: Port advertised in urls (optional, defaults to `port`)
  902. ## Authentication
  904. ### :admin_token
  906. 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 or `x-admin-token` HTTP header. Example:
  908. ```elixir
  909. config :pleroma, :admin_token, "somerandomtoken"
  910. ```
  912. You can then do
  914. ```shell
  915. curl "http://localhost:4000/api/v1/pleroma/admin/users/invites?admin_token=somerandomtoken"
  916. ```
  918. or
  920. ```shell
  921. curl -H "X-Admin-Token: somerandomtoken" "http://localhost:4000/api/v1/pleroma/admin/users/invites"
  922. ```
  924. Warning: it's discouraged to use this feature because of the associated security risk: static / rarely changed instance-wide token is much weaker compared to email-password pair of a real admin user; consider using HTTP Basic Auth or OAuth-based authentication instead.
  926. ### :auth
  928. Authentication / authorization settings.
  930. * `auth_template`: authentication form template. By default it's `show.html` which corresponds to `lib/pleroma/web/templates/o_auth/o_auth/show.html.eex`.
  931. * `oauth_consumer_template`: 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`.
  932. * `oauth_consumer_strategies`: the list of enabled OAuth consumer strategies; by default it's set by `OAUTH_CONSUMER_STRATEGIES` environment variable. Each entry in this space-delimited string should be of format `<strategy>` or `<strategy>:<dependency>` (e.g. `twitter` or `keycloak:ueberauth_keycloak_strategy` in case dependency is named differently than `ueberauth_<strategy>`).
  934. ### Pleroma.Web.Auth.Authenticator
  936. * `Pleroma.Web.Auth.PleromaAuthenticator`: default database authenticator.
  937. * `Pleroma.Web.Auth.LDAPAuthenticator`: LDAP authentication.
  939. ### :ldap
  941. Use LDAP for user authentication.  When a user logs in to the Pleroma
  942. instance, the name and password will be verified by trying to authenticate
  943. (bind) to an LDAP server.  If a user exists in the LDAP directory but there
  944. is no account with the same name yet on the Pleroma instance then a new
  945. Pleroma account will be created with the same name as the LDAP user name.
  947. * `enabled`: enables LDAP authentication
  948. * `host`: LDAP server hostname
  949. * `port`: LDAP port, e.g. 389 or 636
  950. * `ssl`: true to use SSL, usually implies the port 636
  951. * `sslopts`: additional SSL options
  952. * `tls`: true to start TLS, usually implies the port 389
  953. * `tlsopts`: additional TLS options
  954. * `base`: LDAP base, e.g. "dc=example,dc=com"
  955. * `uid`: LDAP attribute name to authenticate the user, e.g. when "cn", the filter will be "cn=username,base"
  957. Note, if your LDAP server is an Active Directory server the correct value is commonly `uid: "cn"`, but if you use an
  958. OpenLDAP server the value may be `uid: "uid"`.
  960. ### :oauth2 (Pleroma as OAuth 2.0 provider settings)
  962. OAuth 2.0 provider settings:
  964. * `token_expires_in` - The lifetime in seconds of the access token.
  965. * `issue_new_refresh_token` - Keeps old refresh token or generate new refresh token when to obtain an access token.
  966. * `clean_expired_tokens` - Enable a background job to clean expired oauth tokens. Defaults to `false`.
  968. OAuth 2.0 provider and related endpoints:
  970. * `POST /api/v1/apps` creates client app basing on provided params.
  971. * `GET/POST /oauth/authorize` renders/submits authorization form.
  972. * `POST /oauth/token` creates/renews OAuth token.
  973. * `POST /oauth/revoke` revokes provided OAuth token.
  974. * `GET /api/v1/accounts/verify_credentials` (with proper `Authorization` header or `access_token` URI param) returns user info on requester (with `acct` field containing local nickname and `fqn` field containing fully-qualified nickname which could generally be used as email stub for OAuth software that demands email field in identity endpoint response, like Peertube).
  976. ### OAuth consumer mode
  978. OAuth consumer mode allows sign in / sign up via external OAuth providers (e.g. Twitter, Facebook, Google, Microsoft, etc.).
  979. Implementation is based on Ueberauth; see the list of [available strategies](https://github.com/ueberauth/ueberauth/wiki/List-of-Strategies).
  981. !!! note
  982.     Each strategy is shipped as a separate dependency; in order to get the strategies, run `OAUTH_CONSUMER_STRATEGIES="..." mix deps.get`, e.g. `OAUTH_CONSUMER_STRATEGIES="twitter facebook google microsoft" mix deps.get`.  The server should also be started with `OAUTH_CONSUMER_STRATEGIES="..." mix phx.server` in case you enable any strategies.
  984. !!! note
  985.     Each strategy requires separate setup (on external provider side and Pleroma side). Below are the guidelines on setting up most popular strategies.
  987. !!! note
  988.     Make sure that `"SameSite=Lax"` is set in `extra_cookie_attrs` when you have this feature enabled. OAuth consumer mode will not work with `"SameSite=Strict"`
  990. * For Twitter, [register an app](https://developer.twitter.com/en/apps), configure callback URL to https://<your_host>/oauth/twitter/callback
  992. * For Facebook, [register an app](https://developers.facebook.com/apps), configure callback URL to https://<your_host>/oauth/facebook/callback, enable Facebook Login service at https://developers.facebook.com/apps/<app_id>/fb-login/settings/
  994. * For Google, [register an app](https://console.developers.google.com), configure callback URL to https://<your_host>/oauth/google/callback
  996. * For Microsoft, [register an app](https://portal.azure.com), configure callback URL to https://<your_host>/oauth/microsoft/callback
  998. Once the app is configured on external OAuth provider side, add app's credentials and strategy-specific settings (if any — e.g. see Microsoft below) to `config/prod.secret.exs`,
  999. per strategy's documentation (e.g. [ueberauth_twitter](https://github.com/ueberauth/ueberauth_twitter)). Example config basing on environment variables:
  1001. ```elixir
  1002. # Twitter
  1003. config :ueberauth, Ueberauth.Strategy.Twitter.OAuth,
  1004.   consumer_key: System.get_env("TWITTER_CONSUMER_KEY"),
  1005.   consumer_secret: System.get_env("TWITTER_CONSUMER_SECRET")
  1007. # Facebook
  1008. config :ueberauth, Ueberauth.Strategy.Facebook.OAuth,
  1009.   client_id: System.get_env("FACEBOOK_APP_ID"),
  1010.   client_secret: System.get_env("FACEBOOK_APP_SECRET"),
  1011.   redirect_uri: System.get_env("FACEBOOK_REDIRECT_URI")
  1013. # Google
  1014. config :ueberauth, Ueberauth.Strategy.Google.OAuth,
  1015.   client_id: System.get_env("GOOGLE_CLIENT_ID"),
  1016.   client_secret: System.get_env("GOOGLE_CLIENT_SECRET"),
  1017.   redirect_uri: System.get_env("GOOGLE_REDIRECT_URI")
  1019. # Microsoft
  1020. config :ueberauth, Ueberauth.Strategy.Microsoft.OAuth,
  1021.   client_id: System.get_env("MICROSOFT_CLIENT_ID"),
  1022.   client_secret: System.get_env("MICROSOFT_CLIENT_SECRET")
  1024. config :ueberauth, Ueberauth,
  1025.   providers: [
  1026.     microsoft: {Ueberauth.Strategy.Microsoft, [callback_params: []]}
  1027.   ]
  1029. # Keycloak
  1030. # Note: make sure to add `keycloak:ueberauth_keycloak_strategy` entry to `OAUTH_CONSUMER_STRATEGIES` environment variable
  1031. keycloak_url = "https://publicly-reachable-keycloak-instance.org:8080"
  1033. config :ueberauth, Ueberauth.Strategy.Keycloak.OAuth,
  1034.   client_id: System.get_env("KEYCLOAK_CLIENT_ID"),
  1035.   client_secret: System.get_env("KEYCLOAK_CLIENT_SECRET"),
  1036.   site: keycloak_url,
  1037.   authorize_url: "#{keycloak_url}/auth/realms/master/protocol/openid-connect/auth",
  1038.   token_url: "#{keycloak_url}/auth/realms/master/protocol/openid-connect/token",
  1039.   userinfo_url: "#{keycloak_url}/auth/realms/master/protocol/openid-connect/userinfo",
  1040.   token_method: :post
  1042. config :ueberauth, Ueberauth,
  1043.   providers: [
  1044.     keycloak: {Ueberauth.Strategy.Keycloak, [uid_field: :email]}
  1045.   ]
  1046. ```
  1048. ## Link parsing
  1050. ### :uri_schemes
  1051. * `valid_schemes`: List of the scheme part that is considered valid to be an URL.
  1053. ### Pleroma.Formatter
  1055. Configuration for Pleroma's link formatter which parses mentions, hashtags, and URLs.
  1057. * `class` - specify the class to be added to the generated link (default: `false`)
  1058. * `rel` - specify the rel attribute (default: `ugc`)
  1059. * `new_window` - adds `target="_blank"` attribute (default: `false`)
  1060. * `truncate` - Set to a number to truncate URLs longer then the number. Truncated URLs will end in `...` (default: `false`)
  1061. * `strip_prefix` - Strip the scheme prefix (default: `false`)
  1062. * `extra` - link URLs with rarely used schemes (magnet, ipfs, irc, etc.) (default: `true`)
  1063. * `validate_tld` - Set to false to disable TLD validation for URLs/emails. Can be set to :no_scheme to validate TLDs only for urls without a scheme (e.g `example.com` will be validated, but `http://example.loki` won't) (default: `:no_scheme`)
  1065. Example:
  1067. ```elixir
  1068. config :pleroma, Pleroma.Formatter,
  1069.   class: false,
  1070.   rel: "ugc",
  1071.   new_window: false,
  1072.   truncate: false,
  1073.   strip_prefix: false,
  1074.   extra: true,
  1075.   validate_tld: :no_scheme
  1076. ```
  1078. ## Custom Runtime Modules (`:modules`)
  1080. * `runtime_dir`: A path to custom Elixir modules (such as MRF policies).
  1082. ## :configurable_from_database
  1084. Boolean, enables/disables in-database configuration. Read [Transferring the config to/from the database](../administration/CLI_tasks/config.md) for more information.
  1086. ## :database_config_whitelist
  1088. List of valid configuration sections which are allowed to be configured from the
  1089. database. Settings stored in the database before the whitelist is configured are
  1090. still applied, so it is suggested to only use the whitelist on instances that
  1091. have not migrated the config to the database.
  1093. Example:
  1094. ```elixir
  1095. config :pleroma, :database_config_whitelist, [
  1096.   {:pleroma, :instance},
  1097.   {:pleroma, Pleroma.Web.Metadata},
  1098.   {:auto_linker}
  1099. ]
  1100. ```
  1102. ### Multi-factor authentication -  :two_factor_authentication
  1103. * `totp` - a list containing TOTP configuration
  1104.   - `digits` - Determines the length of a one-time pass-code in characters. Defaults to 6 characters.
  1105.   - `period` - a period for which the TOTP code will be valid in seconds. Defaults to 30 seconds.
  1106. * `backup_codes` - a list containing backup codes configuration
  1107.   - `number` - number of backup codes to generate.
  1108.   - `length` - backup code length. Defaults to 16 characters.
  1110. ## Restrict entities access for unauthenticated users
  1112. ### :restrict_unauthenticated
  1114. Restrict access for unauthenticated users to timelines (public and federated), user profiles and statuses.
  1116. * `timelines`: public and federated timelines
  1117.   * `local`: public timeline
  1118.   * `federated`: federated timeline (includes public timeline)
  1119. * `profiles`: user profiles
  1120.   * `local`
  1121.   * `remote`
  1122. * `activities`: statuses
  1123.   * `local`
  1124.   * `remote`
  1126. Note: when `:instance, :public` is set to `false`, all `:restrict_unauthenticated` items be effectively set to `true` by default. If you'd like to allow unauthenticated access to specific API endpoints on a private instance, please explicitly set `:restrict_unauthenticated` to non-default value in `config/prod.secret.exs`.
  1128. Note: setting `restrict_unauthenticated/timelines/local` to `true` has no practical sense if `restrict_unauthenticated/timelines/federated` is set to `false` (since local public activities will still be delivered to unauthenticated users as part of federated timeline).
  1130. ## Pleroma.Web.ApiSpec.CastAndValidate
  1132. * `:strict` a boolean, enables strict input validation (useful in development, not recommended in production). Defaults to `false`.
  1134. ## :instances_favicons
  1136. Control favicons for instances.
  1138. * `enabled`: Allow/disallow displaying and getting instances favicons
  1140. ## Pleroma.User.Backup
  1142. !!! note
  1143.     Requires enabled email
  1145. * `:purge_after_days` an integer, remove backup achieves after N days.
  1146. * `:limit_days` an integer, limit user to export not more often than once per N days.
  1147. * `:dir` a string with a path to backup temporary directory or `nil` to let Pleroma choose temporary directory in the following order:
  1148.     1. the directory named by the TMPDIR environment variable
  1149.     2. the directory named by the TEMP environment variable
  1150.     3. the directory named by the TMP environment variable
  1151.     4. C:\TMP on Windows or /tmp on Unix-like operating systems
  1152.     5. as a last resort, the current working directory
  1154. ## Frontend management
  1156. Frontends in Pleroma are swappable - you can specify which one to use here.
  1158. You can set a frontends for the key `primary` and `admin` and the options of `name` and `ref`. This will then make Pleroma serve the frontend from a folder constructed by concatenating the instance static path, `frontends` and the name and ref.
  1160. The key `primary` refers to the frontend that will be served by default for general requests. The key `admin` refers to the frontend that will be served at the `/pleroma/admin` path.
  1162. If you don't set anything here, the bundled frontends will be used.
  1164. Example:
  1166. ```
  1167. config :pleroma, :frontends,
  1168.   primary: %{
  1169.     "name" => "pleroma",
  1170.     "ref" => "stable"
  1171.   },
  1172.   admin: %{
  1173.     "name" => "admin",
  1174.     "ref" => "develop"
  1175.   }
  1176. ```
  1178. This would serve the frontend from the the folder at `$instance_static/frontends/pleroma/stable`. You have to copy the frontend into this folder yourself. You can choose the name and ref any way you like, but they will be used by mix tasks to automate installation in the future, the name referring to the project and the ref referring to a commit.
  1180. ## Ephemeral activities (Pleroma.Workers.PurgeExpiredActivity)
  1182. Settings to enable and configure expiration for ephemeral activities
  1184. * `:enabled` - enables ephemeral activities creation
  1185. * `:min_lifetime` - minimum lifetime for ephemeral activities (in seconds). Default: 10 minutes.
  1187. ## ConcurrentLimiter
  1189. Settings to restrict concurrently running jobs. Jobs which can be configured:
  1191. * `Pleroma.Web.RichMedia.Helpers` - generating link previews of URLs in activities
  1192. * `Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy` - warming remote media cache via MediaProxyWarmingPolicy
  1194. Each job has these settings:
  1196. * `:max_running` - max concurrently runnings jobs
  1197. * `:max_waiting` - max waiting jobs