This was reported by @remimarenco on gitter. The problem is that we are
are setting the environment variables
GALAXY_CONFIG_NGINX_X_ACCEL_REDIRECT_BASE,
GALAXY_CONFIG_NGINX_X_ARCHIVE_FILES_BASE,
and GALAXY_CONFIG_NGINX_UPLOAD_PATH as a composite of
NGINX_GALAXY_LOCATION plus the specific path. In docker we are appending
all current (i.e user-specified variables) to /etc/default/supervisor
and then we source these variables. The problem is that by default we
are setting NGINX_GALAXY_LOCATION="" (i.e no prefix). The following
order would be sourced currently:
This breaks uploading and downloading files for instances with a proxy
prefix, while they appear otherwise functional.
The new approach is to not append the current env vars in the docker
startup script, but to set these variables via ansible. Sourcing
/etc/default/supervisor before starting supervisor will then load the
environment variables into the current session.
This was reported by @remimarenco on gitter. The problem is that we are are setting the environment variables
GALAXY_CONFIG_NGINX_X_ACCEL_REDIRECT_BASE
,GALAXY_CONFIG_NGINX_X_ARCHIVE_FILES_BASE
, andGALAXY_CONFIG_NGINX_UPLOAD_PATH
as a composite of NGINX_GALAXY_LOCATION plus the specific path. In docker we are appending all current (i.e user-specified variables) to /etc/default/supervisor and then we source these variables. The problem is that by default we are setting NGINX_GALAXY_LOCATION="" (i.e no prefix). The following order would be sourced currently:This breaks uploading and downloading files for instances with a proxy prefix, while they appear otherwise functional.
The new approach is to not append the current env vars in the docker startup script, but to set these variables via ansible. Sourcing /etc/default/supervisor before starting supervisor will then load the environment variables into the current session.