I’m trying to use a cdn for deployment of application assets, and I"d like to be able to maintain multiple versions of these assets in the cdn, so when we do new deploys, the application can request the new versions of the assets, and we can easily test our and/or roll back between multiple versions of assets when different apps get deployed. To do so, I’m setting up an s3 bucket with prefixes corresponding to version numbers of the application, IE: /v1.2.3/packs, /v1.2.3/assets, etc.
For assets compilation, we’re using - rails asset pipeline, shakapacker, and dart-sass (part of pipeline).
What would be the recommended configuration to achieve this setup? I’ve been trying different combinations of config.assets.prefix and config.asset_host and have had different levels of success but nothing that has completely worked for all cases yet.
Test Case 1:
- Set
prefixto/assets - Set
asset_hosttocdn.url.com/v1.2.3/ - upload files from
public/→ s3://bucket/v1.2.3/
Outcome:
- shakapacker assets work fine
- rails assets (compiled css) references files /assets/* instead of
/v1.2.3/assets/*
Test Case 2:
- Set
prefixto/v1.2.3/assets - Set
asset_hosttocdn.url.com - upload files from
public/v1.2.3/→ s3://bucket/v1.2.3/
Outcome:
- rails assets get put in /public/v1.2.3/assets which isn’t ideal but acceptable
- rails assets load correctly from public cdn
- shakapacker assets get put in /public/packs
- shakapacker assets do not load correctly in this case
Other:
We are currently on rails 7.0. Shakapacker is updated to 7.2.2
