yep, more or less how approach it. 1. build js,css,img assets 2. upload assets to CDN under unique urls (at build time, for any build that may or may not prod

yep, more or less how approach it. 1. build js,css,img assets 2. upload assets to CDN under unique urls (at build time, for any build that may or may not produce a deployable container) 3. build docker container with server that serves dynamic html referencing those assets 4. deploy said container Main advantages for me: 1. easy to rollback 2. graceful rollover, all assets any deployed container can reference will always exist, even if multiple versions are deployed at the same time during deployment 3. immutable === cacheable forever 4. CDN always "warm"