125bb7dac1
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. |
||
|---|---|---|
| .. | ||
| mail_receiver | ||
| plugins | ||
| rubyEnv | ||
| action_mailer_ca_cert.patch | ||
| admin_create.patch | ||
| auto_generated_path.patch | ||
| default.nix | ||
| nixos_defaults.patch | ||
| notification_email.patch | ||
| plugin_gem_api_version.patch | ||
| unicorn_logging_and_timeout.patch | ||
| update.py | ||
| use_mv_instead_of_rename.patch | ||