talyz 125bb7dac1 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.		2021-12-06 14:21:39 +01:00
..
mail_receiver
plugins	discourse.plugins: Update all plugins to their latest versions	2021-12-02 10:43:14 +01:00
rubyEnv
action_mailer_ca_cert.patch
admin_create.patch
auto_generated_path.patch
default.nix	discourse: Don't patch the public path	2021-12-06 14:21:39 +01:00
nixos_defaults.patch
notification_email.patch
plugin_gem_api_version.patch
unicorn_logging_and_timeout.patch
update.py	discourse: update.py: Improve version handling, use pinned plugins	2021-12-02 11:55:07 +01:00
use_mv_instead_of_rename.patch