At the moment there are two groups of build commands:
- Build: Runs during the docker build process
- Init: Run before the instance starts
It would be really handy to have a third group which runs once the cutover has happened and the new instance is the live version of the app.
For example, this would be where to stick the static cache warm instructions, to avoid the first few page warms being from the old instance.
This is a bit of a unique question but it does make sense, that said it is quite complex on our side and it does change the commands which are always quite complex.
My recommendation (for now at least) is to fire off a job on deployment which uses the Ploi Cloud API to check the latest deployment and waits till it is live, and once it is live to kick off the warm.
-
Steve Parks moved item to project Applications
1 week ago -
Steve Parks created the item
1 week ago