2019-04-07 21:50:36 +09:00
#━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
# Misskey configuration
#━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-02-17 13:34:50 +09:00
# ┌──────────────────────────────┐
#───┘ a boring but important thing └────────────────────────────
#
# First of all, let me tell you a story that may possibly be
# boring to you and possibly important to you.
#
# Misskey is licensed under the AGPLv3 license. This license is
# known to be often misunderstood. Please read the following
# instructions carefully and select the appropriate option so
# that you do not negligently cause a license violation.
#
# --------
# Option 1: If you host Misskey AS-IS (without any changes to
# the source code. forks are not included).
#
# Step 1: Congratulations! You don't need to do anything.
# --------
# Option 2: If you have made changes to the source code (forks
# are included) and publish a Git repository of source
# code. There should be no access restrictions on
# this repository. Strictly speaking, it doesn't have
# to be a Git repository, but you'll probably use Git!
#
# Step 1: Build and run the Misskey server first.
# Step 2: Open <https://your.misskey.example/admin/settings> in
# your browser with the administrator account.
# Step 3: Enter the URL of your Git repository in the
# "Repository URL" field.
# --------
# Option 3: If neither of the above applies to you.
# (In this case, the source code should be published
# on the Misskey interface. IT IS NOT ENOUGH TO
2024-03-09 17:55:41 +09:00
# DISCLOSE THE SOURCE CODE WHEN A USER REQUESTS IT BY
2024-02-17 13:34:50 +09:00
# E-MAIL OR OTHER MEANS. If you are not satisfied
# with this, it is recommended that you read the
# license again carefully. Anyway, enabling this
# option will automatically generate and publish a
# tarball at build time, protecting you from
# inadvertent license violations. (There is no legal
# guarantee, of course.) The tarball will generated
# from the root directory of your codebase. So it is
# also recommended to check <built/tarball> directory
# once after building and before activating the server
# to avoid ACCIDENTAL LEAKING OF SENSITIVE INFORMATION.
# To prevent certain files from being included in the
# tarball, add a glob pattern after line 15 in
# <scripts/tarball.mjs>. DO NOT FORGET TO BUILD AFTER
# ENABLING THIS OPTION!)
#
# Step 1: Uncomment the following line.
#
# publishTarballInsteadOfProvideRepositoryUrl: true
2019-04-07 21:50:36 +09:00
# ┌─────┐
#───┘ URL └─────────────────────────────────────────────────────
2018-10-02 11:59:12 +09:00
# Final accessible URL seen by a user.
url : https://example.tld/
2019-07-03 20:31:52 +09:00
# ONCE YOU HAVE STARTED THE INSTANCE, DO NOT CHANGE THE
# URL SETTINGS AFTER THAT!
2019-04-07 21:50:36 +09:00
# ┌───────────────────────┐
#───┘ Port and TLS settings └───────────────────────────────────
2018-10-02 11:59:12 +09:00
#
2022-03-08 23:23:18 +09:00
# Misskey requires a reverse proxy to support HTTPS connections.
2018-10-02 11:59:12 +09:00
#
# +----- https://example.tld/ ------------+
# +------+ |+-------------+ +----------------+|
# | User | ---> || Proxy (443) | ---> | Misskey (3000) ||
# +------+ |+-------------+ +----------------+|
# +---------------------------------------+
2018-07-15 02:09:55 +09:00
#
2022-03-08 23:23:18 +09:00
# You need to set up a reverse proxy. (e.g. nginx)
# An encrypted connection with HTTPS is highly recommended
# because tokens may be transferred in GET requests.
2018-07-15 02:09:55 +09:00
2022-03-08 23:23:18 +09:00
# The port that your Misskey server should listen on.
port : 3000
2018-07-14 23:20:30 +09:00
2023-09-27 09:32:36 +09:00
# You can also use UNIX domain socket.
2023-07-17 14:12:02 +09:00
# socket: /path/to/misskey.sock
# chmodSocket: '777'
2019-04-07 21:50:36 +09:00
# ┌──────────────────────────┐
#───┘ PostgreSQL configuration └────────────────────────────────
2017-11-23 05:43:00 +09:00
2019-04-07 21:50:36 +09:00
db :
2017-11-23 05:43:00 +09:00
host : localhost
2019-04-07 21:50:36 +09:00
port : 5432
# Database name
2018-07-15 02:29:50 +09:00
db : misskey
2019-04-07 21:50:36 +09:00
# Auth
2018-07-14 22:42:44 +09:00
user : example-misskey-user
pass : example-misskey-pass
2017-11-23 05:43:00 +09:00
2019-06-11 20:49:08 +09:00
# Whether disable Caching queries
#disableCache: true
2019-05-24 03:26:56 +09:00
# Extra Connection options
#extra:
# ssl: true
2023-04-08 15:53:36 +09:00
dbReplications : false
# You can configure any number of replicas here
#dbSlaves:
# -
2023-09-27 09:32:36 +09:00
# host:
# port:
# db:
# user:
# pass:
2023-04-08 15:53:36 +09:00
# -
2023-09-27 09:32:36 +09:00
# host:
# port:
# db:
# user:
# pass:
2023-04-08 15:53:36 +09:00
2019-04-07 21:50:36 +09:00
# ┌─────────────────────┐
#───┘ Redis configuration └─────────────────────────────────────
2019-04-13 19:19:32 +09:00
redis :
host : localhost
port : 6379
2022-06-24 19:22:19 +09:00
#family: 0 # 0=Both, 4=IPv4, 6=IPv6
2019-04-13 19:19:32 +09:00
#pass: example-pass
2019-11-04 20:48:07 +09:00
#prefix: example-prefix
#db: 1
2023-07-20 19:50:31 +09:00
# You can specify more ioredis options...
#username: example-username
2019-04-07 21:50:36 +09:00
2023-04-07 11:20:14 +09:00
#redisForPubsub:
# host: localhost
# port: 6379
# #family: 0 # 0=Both, 4=IPv4, 6=IPv6
# #pass: example-pass
# #prefix: example-prefix
# #db: 1
2023-07-20 19:50:31 +09:00
# # You can specify more ioredis options...
# #username: example-username
2023-04-07 11:20:14 +09:00
2023-04-07 11:27:01 +09:00
#redisForJobQueue:
# host: localhost
# port: 6379
# #family: 0 # 0=Both, 4=IPv4, 6=IPv6
# #pass: example-pass
# #prefix: example-prefix
# #db: 1
2023-07-20 19:50:31 +09:00
# # You can specify more ioredis options...
# #username: example-username
2023-04-07 11:27:01 +09:00
2023-10-03 20:26:11 +09:00
#redisForTimelines:
# host: localhost
# port: 6379
# #family: 0 # 0=Both, 4=IPv4, 6=IPv6
# #pass: example-pass
# #prefix: example-prefix
2023-10-03 20:26:11 +09:00
# #db: 1
# # You can specify more ioredis options...
# #username: example-username
2024-09-20 21:03:53 +09:00
#redisForReactions:
# host: localhost
# port: 6379
# #family: 0 # 0=Both, 4=IPv4, 6=IPv6
# #pass: example-pass
# #prefix: example-prefix
2023-10-03 20:26:11 +09:00
# #db: 1
# # You can specify more ioredis options...
# #username: example-username
2023-05-05 08:52:14 +09:00
# ┌───────────────────────────┐
#───┘ MeiliSearch configuration └─────────────────────────────
2019-04-07 21:50:36 +09:00
2024-02-17 13:34:50 +09:00
# You can set scope to local (default value) or global
2023-12-07 17:00:34 +09:00
# (include notes from remote).
2023-05-05 08:52:14 +09:00
#meilisearch:
2019-04-07 21:50:36 +09:00
# host: localhost
2023-05-05 08:52:14 +09:00
# port: 7700
# apiKey: ''
2023-05-06 04:02:34 +09:00
# ssl: true
2023-05-11 21:09:29 +09:00
# index: ''
2023-11-01 08:42:08 +09:00
# scope: global
2019-04-07 21:50:36 +09:00
# ┌───────────────┐
#───┘ ID generation └───────────────────────────────────────────
2018-11-06 06:24:31 +09:00
2019-04-07 21:50:36 +09:00
# You can select the ID generation method.
# You don't usually need to change this setting, but you can
# change it according to your preferences.
2018-07-14 23:06:46 +09:00
2019-04-07 21:50:36 +09:00
# Available methods:
2019-04-14 01:40:29 +09:00
# aid ... Short, Millisecond accuracy
2023-09-06 18:33:51 +09:00
# aidx ... Millisecond accuracy
2019-04-14 01:40:29 +09:00
# meid ... Similar to ObjectID, Millisecond accuracy
# ulid ... Millisecond accuracy
# objectid ... This is left for backward compatibility
2019-04-07 21:50:36 +09:00
2019-04-25 12:24:18 +09:00
# ONCE YOU HAVE STARTED THE INSTANCE, DO NOT CHANGE THE
# ID SETTINGS AFTER THAT!
2023-09-06 18:33:51 +09:00
id : 'aidx'
2019-04-07 21:50:36 +09:00
2024-05-28 17:06:33 +09:00
# ┌────────────────┐
#───┘ Error tracking └──────────────────────────────────────────
# Sentry is available for error tracking.
# See the Sentry documentation for more details on options.
#sentryForBackend:
# enableNodeProfiling: true
# options:
# dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0'
#sentryForFrontend:
# options:
# dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0'
2019-04-07 21:50:36 +09:00
# ┌─────────────────────┐
#───┘ Other configuration └─────────────────────────────────────
2019-02-06 19:36:44 +09:00
# Whether disable HSTS
#disableHsts: true
2019-08-27 05:33:24 +09:00
# Number of worker processes
2018-10-11 15:50:27 +09:00
#clusterLimit: 1
2019-05-07 17:49:25 +09:00
2019-08-27 05:33:24 +09:00
# Job concurrency per worker
enhance: account migration (#10592)
* copy block and mute then create follow and unfollow jobs
* copy block and mute and update lists when detecting an account has moved
* no need to care promise orders
* refactor updating actor and target
* automatically accept if a locked account had accepted an old account
* fix exception format
* prevent the old account from calling some endpoints
* do not unfollow when moving
* adjust following and follower counts
* check movedToUri when receiving a follow request
* skip if no need to adjust
* Revert "disable account migration"
This reverts commit 2321214c98591bcfe1385c1ab5bf0ff7b471ae1d.
* fix translation specifier
* fix checking alsoKnownAs and uri
* fix updating account
* fix refollowing locked account
* decrease followersCount if followed by the old account
* adjust following and followers counts when unfollowing
* fix copying mutings
* prohibit moved account from moving again
* fix move service
* allow app creation after moving
* fix lint
* remove unnecessary field
* fix cache update
* add e2e test
* add e2e test of accepting the new account automatically
* force follow if any error happens
* remove unnecessary joins
* use Array.map instead of for const of
* ユーザーリストの移行は追加のみを行う
* nanka iroiro
* fix misskey-js?
* :v:
* 移行を行ったアカウントからのフォローリクエストの自動許可を調整
* newUriを外に出す
* newUriを外に出す2
* clean up
* fix newUri
* prevent moving if the destination account has already moved
* set alsoKnownAs via /i/update
* fix database initialization
* add return type
* prohibit updating alsoKnownAs after moving
* skip to add to alsoKnownAs if toUrl is known
* skip adding to the list if it already has
* use Acct.parse instead
* rename error code
* :art:
* 制限を5から10に緩和
* movedTo(Uri), alsoKnownAsはユーザーidを返すように
* test api res
* fix
* 元アカウントはミュートし続ける
* :art:
* unfollow
* fix
* getUserUriをUserEntityServiceに
* ?
* job!
* :art:
* instance => server
* accountMovedShort, forbiddenBecauseYouAreMigrated
* accountMovedShort
* fix test
* import, pin禁止
* 実績を凍結する
* clean up
* :v:
* change message
* ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに
* Revert "ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに"
This reverts commit 3bd7be35d8aa455cb01ae58f8172a71a50485db1.
* validateAlsoKnownAs
* 移行後2時間以内はインポート可能なファイルサイズを拡大
* clean up
* どうせactorをupdatePersonで更新するならupdatePersonしか移行処理を発行しないことにする
* handle error?
* リモートからの移行処理の条件を是正
* log, port
* fix
* fix
* enhance(dev): non-production環境でhttpサーバー間でもユーザー、ノートの連合が可能なように
* refactor (use checkHttps)
* MISSKEY_WEBFINGER_USE_HTTP
* Environment Variable readme
* NEVER USE IN PRODUCTION
* fix punyHost
* fix indent
* fix
* experimental
---------
Co-authored-by: tamaina <tamaina@hotmail.co.jp>
Co-authored-by: syuilo <Syuilotan@yahoo.co.jp>
2023-04-30 00:09:29 +09:00
#deliverJobConcurrency: 128
#inboxJobConcurrency: 16
2024-01-28 15:08:45 +09:00
#relationshipJobConcurrency: 16
# What's relationshipJob?:
enhance: account migration (#10592)
* copy block and mute then create follow and unfollow jobs
* copy block and mute and update lists when detecting an account has moved
* no need to care promise orders
* refactor updating actor and target
* automatically accept if a locked account had accepted an old account
* fix exception format
* prevent the old account from calling some endpoints
* do not unfollow when moving
* adjust following and follower counts
* check movedToUri when receiving a follow request
* skip if no need to adjust
* Revert "disable account migration"
This reverts commit 2321214c98591bcfe1385c1ab5bf0ff7b471ae1d.
* fix translation specifier
* fix checking alsoKnownAs and uri
* fix updating account
* fix refollowing locked account
* decrease followersCount if followed by the old account
* adjust following and followers counts when unfollowing
* fix copying mutings
* prohibit moved account from moving again
* fix move service
* allow app creation after moving
* fix lint
* remove unnecessary field
* fix cache update
* add e2e test
* add e2e test of accepting the new account automatically
* force follow if any error happens
* remove unnecessary joins
* use Array.map instead of for const of
* ユーザーリストの移行は追加のみを行う
* nanka iroiro
* fix misskey-js?
* :v:
* 移行を行ったアカウントからのフォローリクエストの自動許可を調整
* newUriを外に出す
* newUriを外に出す2
* clean up
* fix newUri
* prevent moving if the destination account has already moved
* set alsoKnownAs via /i/update
* fix database initialization
* add return type
* prohibit updating alsoKnownAs after moving
* skip to add to alsoKnownAs if toUrl is known
* skip adding to the list if it already has
* use Acct.parse instead
* rename error code
* :art:
* 制限を5から10に緩和
* movedTo(Uri), alsoKnownAsはユーザーidを返すように
* test api res
* fix
* 元アカウントはミュートし続ける
* :art:
* unfollow
* fix
* getUserUriをUserEntityServiceに
* ?
* job!
* :art:
* instance => server
* accountMovedShort, forbiddenBecauseYouAreMigrated
* accountMovedShort
* fix test
* import, pin禁止
* 実績を凍結する
* clean up
* :v:
* change message
* ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに
* Revert "ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに"
This reverts commit 3bd7be35d8aa455cb01ae58f8172a71a50485db1.
* validateAlsoKnownAs
* 移行後2時間以内はインポート可能なファイルサイズを拡大
* clean up
* どうせactorをupdatePersonで更新するならupdatePersonしか移行処理を発行しないことにする
* handle error?
* リモートからの移行処理の条件を是正
* log, port
* fix
* fix
* enhance(dev): non-production環境でhttpサーバー間でもユーザー、ノートの連合が可能なように
* refactor (use checkHttps)
* MISSKEY_WEBFINGER_USE_HTTP
* Environment Variable readme
* NEVER USE IN PRODUCTION
* fix punyHost
* fix indent
* fix
* experimental
---------
Co-authored-by: tamaina <tamaina@hotmail.co.jp>
Co-authored-by: syuilo <Syuilotan@yahoo.co.jp>
2023-04-30 00:09:29 +09:00
# Follow, unfollow, block and unblock(ings) while following-imports, etc. or account migrations.
2019-08-27 05:33:24 +09:00
2020-01-20 14:14:09 +09:00
# Job rate limiter
enhance: account migration (#10592)
* copy block and mute then create follow and unfollow jobs
* copy block and mute and update lists when detecting an account has moved
* no need to care promise orders
* refactor updating actor and target
* automatically accept if a locked account had accepted an old account
* fix exception format
* prevent the old account from calling some endpoints
* do not unfollow when moving
* adjust following and follower counts
* check movedToUri when receiving a follow request
* skip if no need to adjust
* Revert "disable account migration"
This reverts commit 2321214c98591bcfe1385c1ab5bf0ff7b471ae1d.
* fix translation specifier
* fix checking alsoKnownAs and uri
* fix updating account
* fix refollowing locked account
* decrease followersCount if followed by the old account
* adjust following and followers counts when unfollowing
* fix copying mutings
* prohibit moved account from moving again
* fix move service
* allow app creation after moving
* fix lint
* remove unnecessary field
* fix cache update
* add e2e test
* add e2e test of accepting the new account automatically
* force follow if any error happens
* remove unnecessary joins
* use Array.map instead of for const of
* ユーザーリストの移行は追加のみを行う
* nanka iroiro
* fix misskey-js?
* :v:
* 移行を行ったアカウントからのフォローリクエストの自動許可を調整
* newUriを外に出す
* newUriを外に出す2
* clean up
* fix newUri
* prevent moving if the destination account has already moved
* set alsoKnownAs via /i/update
* fix database initialization
* add return type
* prohibit updating alsoKnownAs after moving
* skip to add to alsoKnownAs if toUrl is known
* skip adding to the list if it already has
* use Acct.parse instead
* rename error code
* :art:
* 制限を5から10に緩和
* movedTo(Uri), alsoKnownAsはユーザーidを返すように
* test api res
* fix
* 元アカウントはミュートし続ける
* :art:
* unfollow
* fix
* getUserUriをUserEntityServiceに
* ?
* job!
* :art:
* instance => server
* accountMovedShort, forbiddenBecauseYouAreMigrated
* accountMovedShort
* fix test
* import, pin禁止
* 実績を凍結する
* clean up
* :v:
* change message
* ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに
* Revert "ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに"
This reverts commit 3bd7be35d8aa455cb01ae58f8172a71a50485db1.
* validateAlsoKnownAs
* 移行後2時間以内はインポート可能なファイルサイズを拡大
* clean up
* どうせactorをupdatePersonで更新するならupdatePersonしか移行処理を発行しないことにする
* handle error?
* リモートからの移行処理の条件を是正
* log, port
* fix
* fix
* enhance(dev): non-production環境でhttpサーバー間でもユーザー、ノートの連合が可能なように
* refactor (use checkHttps)
* MISSKEY_WEBFINGER_USE_HTTP
* Environment Variable readme
* NEVER USE IN PRODUCTION
* fix punyHost
* fix indent
* fix
* experimental
---------
Co-authored-by: tamaina <tamaina@hotmail.co.jp>
Co-authored-by: syuilo <Syuilotan@yahoo.co.jp>
2023-04-30 00:09:29 +09:00
#deliverJobPerSec: 128
2023-12-13 08:14:34 +09:00
#inboxJobPerSec: 32
2024-01-28 15:08:45 +09:00
#relationshipJobPerSec: 64
2020-01-20 14:14:09 +09:00
# Job attempts
enhance: account migration (#10592)
* copy block and mute then create follow and unfollow jobs
* copy block and mute and update lists when detecting an account has moved
* no need to care promise orders
* refactor updating actor and target
* automatically accept if a locked account had accepted an old account
* fix exception format
* prevent the old account from calling some endpoints
* do not unfollow when moving
* adjust following and follower counts
* check movedToUri when receiving a follow request
* skip if no need to adjust
* Revert "disable account migration"
This reverts commit 2321214c98591bcfe1385c1ab5bf0ff7b471ae1d.
* fix translation specifier
* fix checking alsoKnownAs and uri
* fix updating account
* fix refollowing locked account
* decrease followersCount if followed by the old account
* adjust following and followers counts when unfollowing
* fix copying mutings
* prohibit moved account from moving again
* fix move service
* allow app creation after moving
* fix lint
* remove unnecessary field
* fix cache update
* add e2e test
* add e2e test of accepting the new account automatically
* force follow if any error happens
* remove unnecessary joins
* use Array.map instead of for const of
* ユーザーリストの移行は追加のみを行う
* nanka iroiro
* fix misskey-js?
* :v:
* 移行を行ったアカウントからのフォローリクエストの自動許可を調整
* newUriを外に出す
* newUriを外に出す2
* clean up
* fix newUri
* prevent moving if the destination account has already moved
* set alsoKnownAs via /i/update
* fix database initialization
* add return type
* prohibit updating alsoKnownAs after moving
* skip to add to alsoKnownAs if toUrl is known
* skip adding to the list if it already has
* use Acct.parse instead
* rename error code
* :art:
* 制限を5から10に緩和
* movedTo(Uri), alsoKnownAsはユーザーidを返すように
* test api res
* fix
* 元アカウントはミュートし続ける
* :art:
* unfollow
* fix
* getUserUriをUserEntityServiceに
* ?
* job!
* :art:
* instance => server
* accountMovedShort, forbiddenBecauseYouAreMigrated
* accountMovedShort
* fix test
* import, pin禁止
* 実績を凍結する
* clean up
* :v:
* change message
* ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに
* Revert "ブロック, フォロー, ミュート, リストのインポートファイルの制限を32MiBに"
This reverts commit 3bd7be35d8aa455cb01ae58f8172a71a50485db1.
* validateAlsoKnownAs
* 移行後2時間以内はインポート可能なファイルサイズを拡大
* clean up
* どうせactorをupdatePersonで更新するならupdatePersonしか移行処理を発行しないことにする
* handle error?
* リモートからの移行処理の条件を是正
* log, port
* fix
* fix
* enhance(dev): non-production環境でhttpサーバー間でもユーザー、ノートの連合が可能なように
* refactor (use checkHttps)
* MISSKEY_WEBFINGER_USE_HTTP
* Environment Variable readme
* NEVER USE IN PRODUCTION
* fix punyHost
* fix indent
* fix
* experimental
---------
Co-authored-by: tamaina <tamaina@hotmail.co.jp>
Co-authored-by: syuilo <Syuilotan@yahoo.co.jp>
2023-04-30 00:09:29 +09:00
#deliverJobMaxAttempts: 12
#inboxJobMaxAttempts: 8
2020-01-20 14:14:09 +09:00
2023-08-20 13:20:01 +09:00
# Local address used for outgoing requests
#outgoingAddress: 127.0.0.1
2019-05-07 17:49:25 +09:00
# IP address family used for outgoing request (ipv4, ipv6 or dual)
#outgoingAddressFamily: ipv4
2019-08-30 08:29:46 +09:00
2024-10-20 13:49:36 +09:00
# Amount of characters that can be used when writing notes. Longer notes will be rejected. (minimum: 1)
#maxNoteLength: 3000
# Amount of characters that will be saved for remote notes. Longer notes will be truncated to this length. (minimum: 1)
#maxRemoteNoteLength: 100000
2024-10-08 10:03:31 +09:00
# Amount of characters that can be used when writing media descriptions (alt text). Longer descriptions will be rejected. (minimum: 1)
2024-10-20 13:49:36 +09:00
#maxAltTextLength: 20000
2024-10-08 10:03:31 +09:00
# Amount of characters that will be saved for remote media descriptions (alt text). Longer descriptions will be truncated to this length. (minimum: 1)
2024-10-20 13:49:36 +09:00
#maxRemoteAltTextLength: 100000
2024-01-01 02:22:02 +09:00
2019-09-02 04:42:52 +09:00
# Proxy for HTTP/HTTPS
#proxy: http://127.0.0.1:3128
2023-01-12 21:03:02 +09:00
proxyBypassHosts :
- api.deepl.com
- api-free.deepl.com
- www.recaptcha.net
- hcaptcha.com
- challenges.cloudflare.com
2020-04-12 20:32:34 +09:00
2019-09-02 04:42:52 +09:00
# Proxy for SMTP/SMTPS
#proxySmtp: http://127.0.0.1:3128 # use HTTP/1.1 CONNECT
#proxySmtp: socks4://127.0.0.1:1080 # use SOCKS4
#proxySmtp: socks5://127.0.0.1:1080 # use SOCKS5
2019-12-20 01:54:28 +09:00
# Media Proxy
2023-02-04 13:38:51 +09:00
# Reference Implementation: https://github.com/misskey-dev/media-proxy
2023-02-12 09:13:47 +09:00
# * Deliver a common cache between instances
# * Perform image compression (on a different server resource than the main process)
2019-12-31 17:23:47 +09:00
#mediaProxy: https://example.com/proxy
2020-10-18 01:46:40 +09:00
2023-08-05 14:03:01 +09:00
# Proxy remote files (default: true)
2023-02-12 09:13:47 +09:00
# Proxy remote files by this instance or mediaProxy to prevent remote files from running in remote domains.
2023-08-05 14:03:01 +09:00
proxyRemoteFiles : true
2022-02-27 13:59:10 +09:00
2023-02-12 09:13:47 +09:00
# Movie Thumbnail Generation URL
# There is no reference implementation.
# For example, Misskey will point to the following URL:
# https://example.com/thumbnail.webp?thumbnail=1&url=https%3A%2F%2Fstorage.example.com%2Fpath%2Fto%2Fvideo.mp4
#videoThumbnailGenerator: https://example.com
2024-07-25 23:37:23 +09:00
# Sign outgoing ActivityPub GET request (default: true)
2022-12-21 15:30:06 +09:00
signToActivityPubGet : true
2024-07-25 23:37:23 +09:00
# Sign outgoing ActivityPub Activities (default: true)
2024-07-27 11:45:07 +09:00
# Linked Data signatures are cryptographic signatures attached to each activity to provide proof of authenticity.
# When using authorized fetch, this is often undesired as any signed activity can be forwarded to a blocked instance by relays and other instances.
# This setting allows admins to disable LD signatures for increased privacy, at the expense of fewer relayed activities and additional inbound fetch (GET) requests.
2024-07-25 23:37:23 +09:00
attachLdSignatureForRelays : true
2023-12-20 21:17:59 +09:00
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
checkActivityPubGetSignature : false
2021-09-03 21:00:44 +09:00
2023-12-07 17:00:34 +09:00
# For security reasons, uploading attachments from the intranet is prohibited,
2024-02-17 13:34:50 +09:00
# but exceptions can be made from the following settings. Default value is "undefined".
2023-12-07 17:00:34 +09:00
# Read changelog to learn more (Improvements of 12.90.0 (2021/09/04)).
2021-09-03 21:00:44 +09:00
#allowedPrivateNetworks: [
# '127.0.0.1/32'
#]
2021-09-04 20:33:14 +09:00
2023-12-22 21:10:21 +09:00
#customMOTD: ['Hello World', 'The sharks rule all', 'Shonks']
2021-09-04 20:33:14 +09:00
# Upload or download file size limits (bytes)
#maxFileSize: 262144000
2023-09-27 09:32:36 +09:00
2024-06-04 01:29:19 +09:00
# timeout and maximum size for imports (e.g. note imports)
#import:
# downloadTimeout: 30
# maxFileSize: 262144000
2023-09-27 09:32:36 +09:00
# PID File of master process
#pidFile: /tmp/misskey.pid