[Bug]: Cloning WordPress service doesn't work to other server, and doesn't clone some vars

[theDanielJLewis]

Error Message and Logs

No errors, but obvious omissions in end results.

Steps to Reproduce

1. Create a WordPress service (try it with MariaDB, since that's what I was using).
2. Add WORDPRESS_CONFIG_EXTRA=$WORDPRESS_CONFIG_EXTRA to the compose file.
3. Populate a WORDPRESS_CONFIG_EXTRA environment variable.
4. Clone the service to a different server
5. Check if that other server actually has the new service. (I checked by looking for the service ID in /var/lib/docker/volumes/.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.360

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04

Additional Information

I discovered a frustrating little bug.

Small aside: it's not possible on a WordPress service to see which server it's actually running on.

When cloning a WordPress service to a different server, two wrong things happen:

1. The service is cloned, but to the same server instead of the other one.
2. Extra environment variables might not be cloning. For example, I added WORDPRESS_CONFIG_EXTRA=$WORDPRESS_CONFIG_EXTRA to my compose file and populated that env var, but the value is blank on the clone.

[zenigma99]

I'm experiencing the same issues with Coolify v4.0.0-beta.360 on my self-hosted installation. The core problem is the inability to move resources between servers. I've tested this with Ghost CMS and several other services, attempting various solutions such as cloning individual deployments and entire projects.

Despite these efforts, all cloned projects and containers persistently remain on the original server. I'm effectively unable to migrate any resources to a different server with Coolify. Here is a screen-recording 👇
https://github.com/user-attachments/assets/c5170b50-ed9c-4926-8a25-d9f3ab3324d6