From 435477c703e29fbe3234f6d26fe8e16263ee2d84 Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Mon, 22 Apr 2019 14:30:24 -0700 Subject: [PATCH] settings: Document changing LOCAL_UPLOADS_DIR. The main point here is that you should use a symlink rather than changing it, since it's more maintenance work to update our nginx configuration to use an alternative path than to just create a symbolic link. Fixes #12157. --- zproject/prod_settings_template.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/zproject/prod_settings_template.py b/zproject/prod_settings_template.py index 42c0c38b14..26ef211639 100644 --- a/zproject/prod_settings_template.py +++ b/zproject/prod_settings_template.py @@ -282,6 +282,11 @@ ENABLE_FILE_LINKS = False # stored in Amazon S3 or another scalable data store here. See docs at: # # https://zulip.readthedocs.io/en/latest/production/upload-backends.html +# +# If you change LOCAL_UPLOADS_DIR to a different path, you will also +# need to manually edit Zulip's nginx configuration to use the new +# path. For that reason, we recommend replacing /home/zulip/uploads +# with a symlink instead of changing LOCAL_UPLOADS_DIR. LOCAL_UPLOADS_DIR = "/home/zulip/uploads" #S3_AUTH_UPLOADS_BUCKET = "" #S3_AVATAR_BUCKET = ""