asset_cache_configuration
Vars | |
| asset_cdn_url | URL the asset_cdn_webroot can be accessed from.
For best results the webserver powering this should return a long cache validity time,
as all assets sent via this transport use hash based urls
if you want to test this locally, you simpily run the localhost-asset-webroot-server.py python3 script
to host assets stored in data/asset-store/ via http://localhost:58715/ |
|---|---|
| asset_cdn_webroot | Local folder to save assets to. Assets will be saved in the format of asset.MD5HASH.EXT or in namespaces/hash/ as ASSET_FILE_NAME or asset.MD5HASH.EXT |
| asset_simple_preload | Whether to make server passively send all browser assets to each client in the background (instead of waiting for them to be needed) |
| asset_transport | Type of asset transport that will be used for asset delivery. Available options are "simple" or "webroot". |
Var Details
asset_cdn_url
URL the asset_cdn_webroot can be accessed from.
For best results the webserver powering this should return a long cache validity time,
as all assets sent via this transport use hash based urls
if you want to test this locally, you simpily run the localhost-asset-webroot-server.py python3 script
to host assets stored in data/asset-store/ via http://localhost:58715/
asset_cdn_webroot
Local folder to save assets to. Assets will be saved in the format of asset.MD5HASH.EXT or in namespaces/hash/ as ASSET_FILE_NAME or asset.MD5HASH.EXT
asset_simple_preload
Whether to make server passively send all browser assets to each client in the background (instead of waiting for them to be needed)
asset_transport
Type of asset transport that will be used for asset delivery. Available options are "simple" or "webroot".