summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-utils
diff options
context:
space:
mode:
authortalyz <kim.lindberger@gmail.com>2021-12-06 14:21:39 +0100
committertalyz <kim.lindberger@gmail.com>2021-12-06 14:21:39 +0100
commit125bb7dac1fcf9829ff93a33ed19665a72872ecd (patch)
tree80376c8ae4ba6cac073a249abc7f52806c3fc014 /pkgs/development/python-modules/python-utils
parent4fb343c87e29bf1f33b49a1bcc210a57d9d42f1d (diff)
discourse: Don't patch the public path
Instead of patching the path to /public in Discourse's sources, make the nginx configuration refer to the symlink in the discourse package which points to the real path. When there is a mismatch between the path nginx serves and the path Discourse thinks it serves, we can run into issues like files not being served - at least when sendfile requests from the ruby app are processed by nginx. The issue I ran into most recently is that backup downloads don't work. Since Discourse refers to the public directory relative to the Rails root in many places, it's much easier to just sync this path to the nginx configuration than trying to patch all occurrences in the sources. This should hopefully mean less potential for breakage in future Discourse releases, too.
Diffstat (limited to 'pkgs/development/python-modules/python-utils')
0 files changed, 0 insertions, 0 deletions