Question Follow symlinks and block scanning of particular directories

[throwaway_account_Alex A]

I'm configuring my site to deploy in such a way that it creates a structure with multiple versions of the site (example.com/deployments/release/<1, 2, 3, etc>
The web hosting root is then set to a symlink (example.com/deployments/current) which points to the latest release directory and is updated with each deployment.

The problem with this method is that the toolkit detects multiple Wordpress installs for this subscription (each release directory) and also appears to look at the absolute path, instead of following the symlink.

1. Is there a way to prevent the Wordpress toolkit from scanning a particular directory?
2. Is there a way that the toolkit will follow the symlink, instead of using the absolute directory path?

Thanks in advance.

 

[throwaway_account_Alex A]

I've altered my deploy script slightly to remove the (symlink to the) wp-config.php file for a previous release, which prevents the Toolkit from scanning for it, however once the site is in the list, this causes it to be marked as "Broken" instead of removing it from the list.

Ideally, it would be very helpful if the Toolkit followed the symlink to the website directory instead of using the absolute path.
Is there any way to enable this functionality?

 

[throwaway_account_Alex A]

Are there any Wordpress Toolkit CLI commands that can be used to help in this regard?
For example, a command that would let me detach/attach an instance?

 

[weltonw]

Are there any Wordpress Toolkit CLI commands that can be used to help in this regard?
For example, a command that would let me detach/attach an instance?

wp-toolkit: WP Toolkit

The wp-toolkit utility allows you to perform certain actions on WordPress installations. Note: This utility is avai...

docs.plesk.com

--detach

 

[throwaway_account_Alex A]

Fantastic, thanks so much john0001! Not sure how I missed that one