When I first load the page after a new deployment, it takes quite some time to load the page as the CSS/JS needs to be rebuilt. This causes a delay in loading the page, and if the first visitor after a deployment is some visitor instead of me, they might leave.
Also, this sometimes runs into some server timeouts, causing not all assets to be build. Then the page is without CSS, and even hard-reloading it does not cause the assets to get built. I'll need to clear all caches and then reload in order to trigger an asset rebuild.
Describe the solution you'd like
A Console command that builds all Bootstrap assets, and that I can include into my deployment script to be run before the symlink is flipped.
Describe alternatives you've considered
try to find out the cause of the timeouts, and increase some threshold in the server settings
automatically crawl the site (or load the start page) as part of the deployment process
sharing typo3temp between releases (which at least avoids the problem as long as the generated files have the same name, i.e., probably as long as I don't upgrade the Bootstrap package)
manually loading the page after each deployment, and clearing all caches if the CSS cannot load
Feature Request
Is your feature request related to a problem?
When I first load the page after a new deployment, it takes quite some time to load the page as the CSS/JS needs to be rebuilt. This causes a delay in loading the page, and if the first visitor after a deployment is some visitor instead of me, they might leave.
Also, this sometimes runs into some server timeouts, causing not all assets to be build. Then the page is without CSS, and even hard-reloading it does not cause the assets to get built. I'll need to clear all caches and then reload in order to trigger an asset rebuild.
Describe the solution you'd like
A Console command that builds all Bootstrap assets, and that I can include into my deployment script to be run before the symlink is flipped.
Describe alternatives you've considered