In a recent thread related to a problem during deployment I discovered something strange.

Here is the thread: https://station.railway.com/questions/service-deployment-clear-my-redis-queue-d1a5b6e7

I have a Laravel application, so I created a pre-deployment script as suggested by the documentation. I customized the script a bit to avoid running the cache:clear command during deployment. It's also a practice recommended in the Laravel documentation.

The problem is that I noticed cache:clear command being executed after every deployment anyway.

Looking at the deployment logs I found something is running commads autonomously, out of the pre-deployment script.

Look at the thread I linked above for a detailed analysis. I also attach the logs to this message.

It seems something runs like two start/stop container sessions, and during the second one it runs a bunch of Laravel commands.

Am I missing something? If something is running commands autonomously why I need a deployment script in the first place? How can I get control of this process? The cache:clear command can be killer for my application because it's at risk of a cache stampede against the database, due for the huge traffic it handle.

The logs refers to this deplyment: e29fc22d-18b3-42aa-97d9-c8c92913aa7b