We are currently overhauling the staging/push-live functionality based on customer feedback. This will be released in November. At the moment "push live" turns the staging site into the live site by re-mapping the domain. What will happen after the update is that the files/databases will be pushed to the existing live site but will leave the original staging site intact for further development.
Issue #1 - clone a site, wp url’s are not updated in either direction - so this is a completely manual process. The wp-config file had to be edited to even get the staging site to load since it was redirecting to the cloned site.
On cloning, the WordPress site URL is updated in the database using wp-cli. However it sounds like maybe this was being overridden in wp-config.php so the change made by Enhance would not take effect.
8Dweb Issue #2 - Push site back - wp URL’s are not updated again - so another manual process (this really upset them since they all said, then this is not a staging system...) The general consensus was that this all seems rudimentary, though they did commend the staging url and ssl cert being automated.
If you're using "push live", this does not currently update the WordPress site url. This is address in the forthcoming update. In the meantime you can do this in the control panel.
8Dweb Issue #3 - There is a real need for this to be both staging and dev... They need to be able to select which content and tables (similar to WPvivid staging) so important content/users/changes on main site are not overwritten (see #4 & #5 for further comments)
This is coming in the update. You will be able to select directories and databases to exclude from the sync.
8Dweb Issue #4 - This is unusable for those wp admins doing all on dev/staging site and only push changes back to main site…. (Think cloud ways; WPvivid, etc..)
This will also be possible after the update.
8Dweb Issue #5 - not really usable as DEV site per sae at this juncture… since it could be insecure during staging, early site dev, or even while using as staging and/or dev to do all changes that get pushed to primary site. There needs to be a method of securing the staging/dev sites from setup
Are you wanting to restrict access to the staging website?