Commits on Sep 11, 2023

1. Asset paths …

   During deployments both the old and new containers will be active for a
   small period of time. There also may be lagging requests for older CSS
   and JS after the deployment.
   
   This can lead to 404s if a request for old assets hits a new container
   or visa-versa.
   
   This PR makes sure that both sets of assets are available throughout the
   deployment from before the new version of the app is booted.
   
   This can be configured by setting the asset path:
   
   ```yaml
   asset_path: "/rails/public/assets"
   ```
   
   The process is:
   1. We extract the assets out of the container, with docker run, docker
   cp, docker stop. Docker run sets the container command to "sleep" so
   this needs to be available in the container.
   2. We create an asset volume directory on the host for the new version
   of the app on the host and copy the assets in there.
   3. If there is a previous deployment we also copy the new assets into
   its asset volume and copy the older assets into the new asset volume.
   4. We start the new container mapping the asset volume over the top of
   the container's asset path.
   
   This means the both the old and new versions have replaced the asset
   path with a volume containing both sets of assets and should be able
   to serve any request during the deployment. The older assets will
   continue to be available until the next deployment.

   

   djmb committed Sep 11, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 0b43936
   • Browse repository at this point

   Copy the full SHA

   0b43936 View commit details

   Browse the repository at this point in the history