Work to investigate and fix this is scheduled to start later this month, @jon_stormbox. We’ll update this post when we have more to share about how this will be solved. Thank you again for reporting this.
Thank you, just downloaded and tested the 9.2.9 Beta and can see this fix has been implemented and even the deletion of the sql backup at end of pulling
Yeah, we zeroed in on a solution where we don’t timestamp the logs, so there will only ever be a “pull” or a “push” log that’s rewritten for each Connect event.
So far this is only in Beta, but we’ll be rolling it out to Stable soon!
Stop timestamping log files within the _wpeprivate folder during pushes to/pulls from WP Engine.
More detail: what has changed?
Local 9.2.9+ will now overwrite the same log and SQL dump files, preventing files from building up with custom timestamps during each push and pull but retaining the last file from each push/pull to assist with debugging and restores:
Old file name
New file name
When is it created?
[sitename]-push-[timestamp].log
local-push.log
During push
[sitename]-pull-[timestamp].log
local-pull.log
During pull
push-[timestamp].sql
local-backup.sql
During push with ‘database’ ticked
Where to find remote logs, plus optional manual cleanup
You can find the above old or new log and SQL dump files in your install at /home/wpe-user/sites/[installname]/_wpeprivate, accessible via SSH.
Local will no longer timestamp new log or dump files from version 9.2.9 onward, but it does not clean up old log or dump files. We found that an extra cleanup step for historic files would slow down every push/pull, and wasn’t needed for new users or those running 9.2.9+.
If you have previously pushed to/pulled from WPE and want to remove “old files” listed above, follow the steps below. It’s important to make sure everyone pushing/pulling to your site is on Local 9.2.9 or higher first.