You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When serving assets from an external path by setting:
serve_locally=False
and assets_external_path=<url to external asset folder>
css, js, and favicon assets are pulled from the external asset directory when the app is initialized, but if I try to use app.get_asset_url(<asset>) it still pulls the asset from the dash directory rather than the external directory.
Would developers be ammenable to a pull request altering the get_asset_url function to look more like below?
For reference get_asset_path is defined in _utils.py as:
defget_asset_path(requests_pathname, asset_path, asset_url_path):
return"/".join(
[
# Only take the first part of the pathnamerequests_pathname.rstrip("/"),
asset_url_path,
asset_path,
]
)
The text was updated successfully, but these errors were encountered:
alexcjohnson
changed the title
[BUG]
[BUG] External assets not reflected in get_asset_url
Jan 15, 2021
When serving assets from an external path by setting:
serve_locally=False
and
assets_external_path=<url to external asset folder>
css, js, and favicon assets are pulled from the external asset directory when the app is initialized, but if I try to use
app.get_asset_url(<asset>)
it still pulls the asset from the dash directory rather than the external directory.Would developers be ammenable to a pull request altering the get_asset_url function to look more like below?
For reference get_asset_path is defined in _utils.py as:
The text was updated successfully, but these errors were encountered: