mina deploy updates the current symlink, but changes only appear in the application after a second execution

[roberio3620]

Hello! I'm new to deployment and infrastructure, and I'm setting up a Continuous Delivery (CD) process using Mina (v1.2.5) on a VPS. I'm facing a curious issue: the mina deploy command runs successfully, updates the current symlink to the new release, but the code changes only appear in the application after I run mina deploy a second time.

Current workflow:

• I have two scripts:

1. One inside the project repository.
2. And another on the VPS.

On the VPS:

1. The script runs git pull in the local repository clone.
2. Then executes mina deploy.

On the first execution, the deploy completes without errors and the current symlink is correctly updated to the new release. However, when accessing the application (API or web), the displayed code is still from the previous version. Only after running mina deploy again do the latest changes actually reflect in the application.

I'm using Mina version v1.2.5, with the standard deploy structure (releases, current, and shared folders), and I haven't been able to figure out what's causing this behavior. If anyone has experienced something similar or has any advice, I’d greatly appreciate it.

[asia653]

You probably need to restart the rails/puma server