You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,12 @@ We support all of the official [environment variables](https://docs.joinmastodon
80
80
81
81
For more information check out the [mastodon documentation](https://docs.joinmastodon.org/).
82
82
83
+
### Running separate sidekiq instances
84
+
85
+
It is currently only supported to run a single queue per container instance *or* all queues in a single container instance.
86
+
87
+
All containers must share the same `/config`` mount and be on a common docker network.
88
+
83
89
### Strict reverse proxies
84
90
85
91
This image automatically redirects to https with a self-signed certificate. If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
@@ -129,6 +135,11 @@ services:
129
135
- AWS_ACCESS_KEY_ID= #optional
130
136
- AWS_SECRET_ACCESS_KEY= #optional
131
137
- S3_ALIAS_HOST= #optional
138
+
- SIDEKIQ_ONLY=false #optional
139
+
- SIDEKIQ_QUEUE= #optional
140
+
- SIDEKIQ_DEFAULT=false #optional
141
+
- SIDEKIQ_THREADS=5 #optional
142
+
- DB_POOL=5 #optional
132
143
volumes:
133
144
- /path/to/appdata/config:/config
134
145
ports:
@@ -173,6 +184,11 @@ docker run -d \
173
184
-e AWS_ACCESS_KEY_ID= `#optional` \
174
185
-e AWS_SECRET_ACCESS_KEY= `#optional` \
175
186
-e S3_ALIAS_HOST= `#optional` \
187
+
-e SIDEKIQ_ONLY=false `#optional` \
188
+
-e SIDEKIQ_QUEUE= `#optional` \
189
+
-e SIDEKIQ_DEFAULT=false `#optional` \
190
+
-e SIDEKIQ_THREADS=5 `#optional` \
191
+
-e DB_POOL=5 `#optional` \
176
192
-p 80:80 \
177
193
-p 443:443 \
178
194
-v /path/to/appdata/config:/config \
@@ -219,6 +235,11 @@ Container images are configured using parameters passed at runtime (such as thos
219
235
|`-e AWS_ACCESS_KEY_ID=`| S3 bucket access key ID |
|`-e S3_ALIAS_HOST=`| Alternate hostname for object fetching if you are front the S3 connections. |
238
+
|`-e SIDEKIQ_ONLY=false`| Only run the sidekiq service in this container instance. For large scale instances that need better queue handling. |
239
+
|`-e SIDEKIQ_QUEUE=`| The name of the sidekiq queue to run in this container. See [notes](https://docs.joinmastodon.org/admin/scaling/#sidekiq-queues). |
240
+
|`-e SIDEKIQ_DEFAULT=false`| Set to `true` on the main container if you're running additional sidekiq instances. It will run the `default` queue. |
241
+
|`-e SIDEKIQ_THREADS=5`| The number of threads for sidekiq to use. See [notes](https://docs.joinmastodon.org/admin/scaling/#sidekiq-threads). |
242
+
|`-e DB_POOL=5`| The size of the DB connection pool, must be *at least* the same as `SIDEKIQ_THREADS`. See [notes](https://docs.joinmastodon.org/admin/scaling/#sidekiq-threads). |
222
243
|`-v /config`| Contains all relevant configuration files. |
223
244
224
245
## Environment variables from files (Docker secrets)
@@ -330,5 +351,6 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
330
351
331
352
## Versions
332
353
354
+
***19.12.22:** - Support separate sidekiq queue instances.
- { env_var: "S3_ALIAS_HOST", env_value: "", desc: "Alternate hostname for object fetching if you are front the S3 connections."}
61
+
- { env_var: "SIDEKIQ_ONLY", env_value: "false", desc: "Only run the sidekiq service in this container instance. For large scale instances that need better queue handling."}
62
+
- { env_var: "SIDEKIQ_QUEUE", env_value: "", desc: "The name of the sidekiq queue to run in this container. See [notes](https://docs.joinmastodon.org/admin/scaling/#sidekiq-queues)."}
63
+
- { env_var: "SIDEKIQ_DEFAULT", env_value: "false", desc: "Set to `true` on the main container if you're running additional sidekiq instances. It will run the `default` queue."}
64
+
- { env_var: "SIDEKIQ_THREADS", env_value: "5", desc: "The number of threads for sidekiq to use. See [notes](https://docs.joinmastodon.org/admin/scaling/#sidekiq-threads)."}
65
+
- { env_var: "DB_POOL", env_value: "5", desc: "The size of the DB connection pool, must be *at least* the same as `SIDEKIQ_THREADS`. See [notes](https://docs.joinmastodon.org/admin/scaling/#sidekiq-threads)."}
61
66
62
67
param_usage_include_ports: true
63
68
param_ports:
@@ -83,11 +88,18 @@ app_setup_block: |
83
88
84
89
For more information check out the [mastodon documentation](https://docs.joinmastodon.org/).
85
90
91
+
### Running separate sidekiq instances
92
+
93
+
It is currently only supported to run a single queue per container instance *or* all queues in a single container instance.
94
+
95
+
All containers must share the same `/config`` mount and be on a common docker network.
96
+
86
97
### Strict reverse proxies
87
98
88
99
This image automatically redirects to https with a self-signed certificate. If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
0 commit comments