UPDATE: I just checked the way markdown-it-bundle is embedded and executed the script_asset_path through the rail console (with slight modifications due to the missing request.env variable!)
According to the script_asset_path, the asset url is correctly generated. Still not sure why this is happening.
EDIT:
It seems to be a known bug
EDIT 2:
I “fixed” it by using the most dirtiest workaround available. Hardcoding the Asset in the nginx config and redirecting it
location ~ markdown-it-bundle-dcd9743077867b3a68d7b723130cb2711dc4c843b018d7bc609f868289402fef.(.*).js {
return 302 https://tosdr-forum.s3.jrbit.de/assets/markdown-it-bundle-dcd9743077867b3a68d7b723130cb2711dc4c843b018d7bc609f868289402fef.$1.js;
}
Did the trick, unless the asset is updated 