Sure you can deactivate them or when deploying but you're dont need them again to be active if you want to perform shifts to your code or update directory from remote one.
Sadly to the sentitive work that this plugin performs it doesn't work center of the box so besides from installing this plugin you need to do additional work..
If you follow this experience note that development-config. php should not be included in your deployments to staging and production and both development-config. php and staging-config. php should in production environment..
These arguments are not going to shift so you need to follow this practice in order to use this plugin correctly..
Once you have installed this plugin recommendation is to do it in development you will notice that new link seems under active plugin of the list.
Once you double-click link that plugin will be added to the list of plugins that need to be active in the resources.
Once you performed complete deploy issues and directory to environment let's say from development to staging you will that these plugins you selected in development to be active only in that environment are active.
This is games as it would be insecure to shift the status of the plugins without knowledge so you need to do automatically by just clicking the.
If you prefer your delivery to be reset automatically without clicking button you can add constant to configuration issue called WP ENV PLUGINS AUTO RESET.
If you use this method you won't see the button in the gallery anymore instead it will be replaced by indicator but keep in mind that the reset process will run time page of page is loaded.
Read more
Related items:
