continuwuation/continuwuity
continuwuation/continuwuity
13
35
Fork 34
Code Issues 103 Pull requests 21 Releases 20 Packages 3 Activity Actions

Improve NGINX reverse proxy setup instructions #971

Open
Anagastes wants to merge 6 commits from Anagastes/continuwuity:main into main
pull from: Anagastes/continuwuity:main
merge into: continuwuation:main
Conversation 9 Commits 6 Files changed 1 +58 -8
Anagastes commented 2025-09-01 17:15:45 +00:00
First-time contributor
Copy link

Added NGINX example with Unix sockets. Helpful for newbies. I've struggled with this a lot, so here's to everyone now. :)

Added NGINX example with Unix sockets. Helpful for newbies. I've struggled with this a lot, so here's to everyone now. :)
docs/deploying/generic.md aktualisiert
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
6baa845274 
Added NGINX example with Unix sockets. Helpful for newbies. I've struggled with this a lot, so here's to everyone now. :)
nex commented 2025-09-10 16:24:46 +00:00
Owner
Copy link

@Anagastes Are you planning to iterate on this further? If not we can review and propose merge once the WIP status is removed :)

@Anagastes Are you planning to iterate on this further? If not we can review and propose merge once the WIP status is removed :)
nex changed title from WIP: docs/deploying/generic.md changed to WIP: Improve NGINX reverse proxy setup instructions 2025-09-10 16:25:56 +00:00
Anagastes commented 2025-09-10 16:52:19 +00:00
Author
First-time contributor
Copy link

Ah, I see. Yes, the process wasn't entirely clear yet :D

I'll do one last check and then remove the WIP.@nex wrote in #971 (comment):

@Anagastes Are you planning to iterate on this further? If not we can review and propose merge once the WIP status is removed :)

Ah, I see. Yes, the process wasn't entirely clear yet :D I'll do one last check and then remove the WIP.@nex wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/971#issuecomment-19761: > @Anagastes Are you planning to iterate on this further? If not we can review and propose merge once the WIP status is removed :)
nex commented 2025-09-10 16:54:14 +00:00
Owner
Copy link

No worries! I'm currently working on improving the issue/PR flows so they'll be clearer in future ^.^

No worries! I'm currently working on improving the issue/PR flows so they'll be clearer in future ^.^
Anagastes changed title from WIP: Improve NGINX reverse proxy setup instructions to Improve NGINX reverse proxy setup instructions 2025-09-10 17:08:41 +00:00
Anagastes force-pushed main from 7bbea1a88f
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
to 11a61d214e
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 50s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 5m33s
Details
2025-09-10 17:08:49 +00:00 Compare
Anagastes force-pushed main from 11a61d214e
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 50s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 5m33s
Details
to 4169f69e6b
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 38s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m16s
Details
2025-09-10 18:43:46 +00:00 Compare
nex force-pushed main from 4169f69e6b
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 38s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m16s
Details
to fa638c7951
All checks were successful
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 36s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 4m24s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
2025-09-11 16:48:43 +00:00 Compare
nex requested review from nex 2025-09-11 16:48:49 +00:00
nex approved these changes 2025-09-17 21:03:32 +00:00
nex force-pushed main from fa638c7951
All checks were successful
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 36s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 4m24s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
to e3f9fe2f34
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 49s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m1s
Details
2025-09-17 21:03:35 +00:00 Compare
tcpipuk force-pushed main from d3fbbade64
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m4s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m16s
Details
Release Docker Image / Build linux-amd64 (release) (pull_request) Successful in 5m47s
Details
Release Docker Image / Build linux-arm64 (release) (pull_request) Successful in 5m58s
Details
Release Docker Image / Create Multi-arch Release Manifest (pull_request) Successful in 4s
Details
Release Docker Image / Build linux-amd64 (max-perf) (pull_request) Successful in 12m40s
Details
Release Docker Image / Build linux-arm64 (max-perf) (pull_request) Successful in 12m37s
Details
Release Docker Image / Create Max-Perf Manifest (pull_request) Successful in 10s
Details
to 869c044059
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m45s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m48s
Details
2025-09-23 06:52:23 +00:00 Compare
ginger force-pushed main from 869c044059
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m45s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m48s
Details
to 333c029f84
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m18s
Details
Release Docker Image / Build linux-amd64 (release) (pull_request) Successful in 3m42s
Details
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Failing after 4m10s
Details
Update flake hashes / update-flake-hashes (pull_request) Failing after 1m56s
Details
Release Docker Image / Build linux-arm64 (release) (pull_request) Successful in 3m1s
Details
Release Docker Image / Create Multi-arch Release Manifest (pull_request) Successful in 4s
Details
Release Docker Image / Build linux-amd64 (max-perf) (pull_request) Successful in 1m38s
Details
Release Docker Image / Build linux-arm64 (max-perf) (pull_request) Successful in 1m44s
Details
Release Docker Image / Create Max-Perf Manifest (pull_request) Successful in 5s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 22m50s
Details
2025-10-13 13:06:24 +00:00 Compare
ginger added this to the 0.5.0 milestone 2025-10-13 13:06:37 +00:00
nex commented 2025-10-15 02:52:53 +00:00
Owner
Copy link

Going to merge this now, if you were going to add LK docs (looking at the reverted commit a few weeks ago) probably worth opening a followup PR

Going to merge this now, if you were going to add LK docs (looking at the reverted commit a few weeks ago) probably worth opening a followup PR
nex requested changes 2025-10-15 02:55:20 +00:00
nex left a comment
Owner
Copy link

noticed a couple things on a final-pass look over

noticed a couple things on a final-pass look over
docs/deploying/generic.md Outdated
@ -168,0 +172,4 @@
Please note that your NGINX must have access to the socket.
In most cases, this is the **www-data** group. For consistency reasons, we change the systemd service.
nex commented 2025-10-15 02:54:29 +00:00
Owner
Copy link
- For security and performance reasons, we recommend Unix sockets with NGINX. 
+ For security and performance reasons, we recommend Unix sockets with NGINX, although plain port proxying is described later for convenience.

Something like this perhaps? nitpicking if anything

```diff - For security and performance reasons, we recommend Unix sockets with NGINX. + For security and performance reasons, we recommend Unix sockets with NGINX, although plain port proxying is described later for convenience. ``` Something like this perhaps? nitpicking if anything
Jade commented 2025-10-15 18:04:12 +00:00
Owner
Copy link

or just 'For the best security and performance, you can use Unix sockets with NGINX. Alternatively, you can use normal TCP proxying'

or just 'For the best security and performance, you can use Unix sockets with NGINX. Alternatively, you can use normal TCP proxying'
docs/deploying/generic.md Outdated
@ -168,0 +203,4 @@
# Synapse-Server responses may be chunked, which is an HTTP/1.1 feature.
proxy_http_version 1.1;
}
```
nex commented 2025-10-15 02:55:03 +00:00
Owner
Copy link

The default value is 20M, perhaps the nginx config should reflect that?

The default value is 20M, perhaps the nginx config should reflect that?
Jade commented 2025-10-15 18:04:52 +00:00
Owner
Copy link

Also we're not synapse, so the comment is off

Also we're not synapse, so the comment is off
Anagastes commented 2025-11-06 20:23:22 +00:00
Author
First-time contributor
Copy link

yeah, my vault... im sorry. its because of my migration from synapse... :S

yeah, my vault... im sorry. its because of my migration from synapse... :S
docs/deploying/generic.md Outdated
@ -174,0 +216,4 @@
- `proxy_pass http://127.0.0.1:6167$request_uri;`
- `proxy_pass http://127.0.0.1:6167;`
Maybe you will check your conf bevor.
nex commented 2025-10-15 02:53:16 +00:00
Owner
Copy link

bevor -> before?

bevor -> before?
nex commented 2025-10-15 03:03:59 +00:00
Owner
Copy link

Actually maybe this should just be rephrased to
Make sure that your IP and port match that on which continuwuity is listening. Check your configuration if you aren't sure.

Actually maybe this should just be rephrased to `Make sure that your IP and port match that on which continuwuity is listening. Check your configuration if you aren't sure.`
Anagastes commented 2025-11-06 20:24:37 +00:00
Author
First-time contributor
Copy link

Sorry... I type quickly... I'm German and sometimes... I'm sorry. I think I should work on my quality in this area...

Sorry... I type quickly... I'm German and sometimes... I'm sorry. I think I should work on my quality in this area...
nex requested changes 2025-10-15 03:04:02 +00:00
docs/deploying/generic.md Outdated
@ -168,0 +176,4 @@
```
User=conduwuit
Group=www-data
```
nex commented 2025-10-15 03:02:23 +00:00
Owner
Copy link
- Please note that your NGINX must have access to the socket.
-
- In most cases, this is the **www-data** group. For consistency reasons, we change the systemd service.
+ Please note that NGINX must have access to the socket. This is typically achieved by making sure the Unix socket is owned by the **www-data** group, so to achieve this we will update the systemd service.

General clarity here.

```diff - Please note that your NGINX must have access to the socket. - - In most cases, this is the **www-data** group. For consistency reasons, we change the systemd service. + Please note that NGINX must have access to the socket. This is typically achieved by making sure the Unix socket is owned by the **www-data** group, so to achieve this we will update the systemd service. ``` General clarity here.
nex commented 2025-10-15 03:02:27 +00:00
Owner
Copy link

Also, I'm not convinced making nginx and continuwuity share a group is a good idea, since the database is also group-readable, and this inherently increases the attack surface since now nginx will have the ability to completely read the database of continuwuity. Perhaps using something like ExecStartPost= to change the permissions of the socket itself to be more permissive (world writable? unsure what the implications on that are) is the more secure option that seems in-scope.

Also, I'm not convinced making nginx and continuwuity share a group is a good idea, since the database is also group-readable, and this inherently increases the attack surface since now nginx will have the ability to completely read the database of continuwuity. Perhaps using something like [`ExecStartPost=`](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#ExecStartPre=) to change the permissions of the socket itself to be more permissive (world writable? unsure what the implications on that are) is the more secure option that seems in-scope.
Jade commented 2025-10-15 18:07:44 +00:00
Owner
Copy link

World-writable would have effectively the same security profile as network sockets AFAIK. I'm sure there's a better permissions-based solution

World-writable would have effectively the same security profile as network sockets AFAIK. I'm sure there's a better permissions-based solution
docs/deploying/generic.md Outdated
@ -174,0 +198,4 @@
}
location ~ ^(/|/_matrix|/_conduwuit) {
nex commented 2025-10-15 03:03:14 +00:00
Owner
Copy link

Haven't used nginx in a hot minute, but shouldn't this be inside the server block?

Haven't used nginx in a hot minute, but shouldn't this be inside the server block?
Anagastes commented 2025-11-06 20:08:04 +00:00
Author
First-time contributor
Copy link

@nex sorry, holidays.

And it should be located within the server block, yes.

But that's just one example. A whole block looks like this.

Would you like to publish an entire finished block? Or small snippets for system administrators who know what they are doing? ;)

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    listen 80;
    listen [::]:80;
    server_name xx.yy.zz;

    include /etc/nginx/templates/ssl.tmpl;

    
location ~ ^(/.well-known/matrix/server) {
   access_log off;
   add_header Access-Control-Allow-Origin *;
   return 200 '{"m.server": "xx.yy.zz:443"}';
   types { } default_type "application/json; charset=utf-8";
}

location ~ ^(/.well-known/matrix/client) {
    access_log off;

    add_header Access-Control-Allow-Origin *;
    add_header Access-Control-Allow-Methods 'GET, POST, PUT, DELETE, OPTIONS';
    add_header Access-Control-Allow-Headers 'X-Requested-With, Content-Type, Authorization';

    return 200 '{"m.homeserver": {"base_url": "https://xx.yy.zz"}}';

    types { } default_type "application/json; charset=utf-8";

}


location ~ ^(/|/_matrix|/_conduwuit) {
    proxy_pass http://unix:/run/conduwuit/conduwuit.sock;
    proxy_set_header X-Forwarded-For $remote_addr;

    # Nginx by default only allows file uploads up to 1M in size
    client_max_body_size 150M;

    # Responses may be chunked, which is an HTTP/1.1 feature.
    proxy_http_version 1.1;

    proxy_max_temp_file_size 1024M;
    client_body_temp_path /tmp;

    proxy_buffer_size          128k;
    proxy_buffers              4 256k;
    proxy_busy_buffers_size    256k;
    proxy_connect_timeout       900;
    proxy_send_timeout          900;
    proxy_read_timeout          900;
    send_timeout                900;
}
}
@nex sorry, holidays. And it should be located within the server block, yes. But that's just one example. A whole block looks like this. Would you like to publish an entire finished block? Or small snippets for system administrators who know what they are doing? ;) ```nginx server { listen 443 ssl http2; listen [::]:443 ssl http2; listen 80; listen [::]:80; server_name xx.yy.zz; include /etc/nginx/templates/ssl.tmpl; location ~ ^(/.well-known/matrix/server) { access_log off; add_header Access-Control-Allow-Origin *; return 200 '{"m.server": "xx.yy.zz:443"}'; types { } default_type "application/json; charset=utf-8"; } location ~ ^(/.well-known/matrix/client) { access_log off; add_header Access-Control-Allow-Origin *; add_header Access-Control-Allow-Methods 'GET, POST, PUT, DELETE, OPTIONS'; add_header Access-Control-Allow-Headers 'X-Requested-With, Content-Type, Authorization'; return 200 '{"m.homeserver": {"base_url": "https://xx.yy.zz"}}'; types { } default_type "application/json; charset=utf-8"; } location ~ ^(/|/_matrix|/_conduwuit) { proxy_pass http://unix:/run/conduwuit/conduwuit.sock; proxy_set_header X-Forwarded-For $remote_addr; # Nginx by default only allows file uploads up to 1M in size client_max_body_size 150M; # Responses may be chunked, which is an HTTP/1.1 feature. proxy_http_version 1.1; proxy_max_temp_file_size 1024M; client_body_temp_path /tmp; proxy_buffer_size 128k; proxy_buffers 4 256k; proxy_busy_buffers_size 256k; proxy_connect_timeout 900; proxy_send_timeout 900; proxy_read_timeout 900; send_timeout 900; } } ```
ginger force-pushed main from 333c029f84
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m18s
Details
Release Docker Image / Build linux-amd64 (release) (pull_request) Successful in 3m42s
Details
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Failing after 4m10s
Details
Update flake hashes / update-flake-hashes (pull_request) Failing after 1m56s
Details
Release Docker Image / Build linux-arm64 (release) (pull_request) Successful in 3m1s
Details
Release Docker Image / Create Multi-arch Release Manifest (pull_request) Successful in 4s
Details
Release Docker Image / Build linux-amd64 (max-perf) (pull_request) Successful in 1m38s
Details
Release Docker Image / Build linux-arm64 (max-perf) (pull_request) Successful in 1m44s
Details
Release Docker Image / Create Max-Perf Manifest (pull_request) Successful in 5s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 22m50s
Details
to 2736b504b9
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m28s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 20m26s
Details
2025-11-06 22:21:21 +00:00 Compare
nex commented 2025-11-06 22:53:17 +00:00
Owner
Copy link

@Anagastes wrote in #971 (comment):

@nex sorry, holidays.

And it should be located within the server block, yes.

But that's just one example. A whole block looks like this.

Would you like to publish an entire finished block? Or small snippets for system administrators who know what they are doing? ;)

I think including a full block somewhere (maybe towards the end) would be handy, but I'm not too bothered - just wanted to make sure it wasn't a mistake :)

Don't worry about the delay, there's no rush!

@Anagastes wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/971#issuecomment-21433: > @nex sorry, holidays. > > And it should be located within the server block, yes. > > But that's just one example. A whole block looks like this. > > Would you like to publish an entire finished block? Or small snippets for system administrators who know what they are doing? ;) I think including a full block somewhere (maybe towards the end) would be handy, but I'm not too bothered - just wanted to make sure it wasn't a mistake :) Don't worry about the delay, there's no rush!
Anagastes force-pushed main from 2736b504b9
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m28s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 20m26s
Details
to 344eb1450f
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m29s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 24m3s
Details
2025-11-10 22:38:44 +00:00 Compare
ginger force-pushed main from 344eb1450f
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m29s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 24m3s
Details
to 9e79293e3c
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m3s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 6m1s
Details
2025-11-12 15:31:43 +00:00 Compare
ginger removed this from the 0.5.0 milestone 2025-11-28 20:52:08 +00:00
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m3s
Required
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 6m1s
Required
Details
This pull request has changes requested by an official reviewer.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u main:Anagastes-main
git switch Anagastes-main
Sign in to join this conversation.
Reviewers
No reviewers
nex
Labels
Clear labels   
Bug

Something isn't working as intended

  
Cherry-picking

Commits picked from other conduit projects

  
Database

This requires or includes changes to the database

  
Dependencies

Something dependency related

  
Dependencies/Renovate

Automatic dependency upgrades by Renovate

  
Difficulty
Easy
Low difficulty to implement - touches few parts of the codebase, low complexity

  
Difficulty
Hard
High difficulty to implement - touches many parts of the codebase, high complexity

  
Difficulty
Medium
Medium difficulty to implement - touches more parts of the codebase, higher complexity

  
Documentation

Improvements or additions to documentation

  
Enhancement

New feature or request

  
Good first issue

Good for newcomers

  
Help wanted

Additional eyes and keyboards are required for this one

  
Inherited

Issues that have been inhereted from the project pre-fork

  
Matrix/Administration

Features pertaining to homeserver administration

  
Matrix/Appservices

Features pertaining to the appservice API

  
Matrix/Auth

Features pertaining to authentication

  
Matrix/Client

Features pertaining to client-to-server interactions

  
Matrix/Core

Issues relating to core matrix functionality, such as state resolution and PDU formats

  
Matrix/Federation

Features pertaining to server-to-server interactions

  
Matrix/Hydra

Issues related to room version 12 and related changes (temporary label)

  
Matrix/MSC

Features pertaining to unstable matrix features

  
Matrix/Media

Features pertaining to media interactions

  
Meta

Related to housekeeping, maintenance, or other repo-meta.

  
Meta/CI

Issues related to CI changes

  
Meta/Packaging

Packaging

  
Priority
Blocking
This issue is blocking the next release

  
Priority
High
This issue is very important

  
Priority
Low
This issue is of a rather low priority

  
Security

This item is related to general security

  
Status/Blocked

This pull request or issue is currently blocked from being merged/closed

  
Status
Confirmed
This issue has enough information and is confirmed

  
Status
Duplicate
This issue or pull request already exists

  
Status
Invalid
This issue doesn't seem right

  
Status
Needs Investigation
This issue needs further investigation

  
Support

Questions or support requests

  
To-Merge

   
Wont fix

This will not be worked on

  
old/ci/cd

Ci/CD

Archived

  
old/rust

Pull requests that update Rust code

Archived

No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!971
No description provided.