Browse Source

Fix assets loading when WEB_DOMAIN ≠ LOCAL_DOMAIN (#6319)

Since 872a0d5bd801c998d911f7da582a60d2f714a710, assets URL are absolute and
not relative. Unfortunately, the domain used to build such URLs is the wrong
one: LOCAL_DOMAIN, and not WEB_DOMAIN, where the assets are stored.
pull/4/head
ThibG 6 years ago
committed by Eugen Rochko
parent
commit
d613dda91d
1 changed files with 1 additions and 1 deletions
  1. +1
    -1
      config/webpack/configuration.js

+ 1
- 1
config/webpack/configuration.js View File

@ -27,7 +27,7 @@ function formatPublicPath(host = '', path = '') {
const output = {
path: resolve('public', settings.public_output_path),
publicPath: formatPublicPath(env.ASSET_HOST || env.LOCAL_DOMAIN, settings.public_output_path),
publicPath: formatPublicPath(env.ASSET_HOST || env.WEB_DOMAIN || env.LOCAL_DOMAIN, settings.public_output_path),
};
module.exports = {

Loading…
Cancel
Save