ByteEditor vs. Local by WP Engine

It's great for quickly cloning an environment down from WP Engine and/or Flywheel servers but can also just be used as a way to setup local environments on your own with manual syncing. If you need to spin up local environments that are not WordPress based then this tool isn't ideal. It can be used for it but it's not design for that.

Incentivized

• Easily clone installs from WP Engine to local envrionments
• 1 click setup of Local WordPress sites for new or existing builds
• Can optionally push back to WP Engine with ease
• Easily change PHP versions
• Integrates with IDE for error reporting

Incentivized

• Interface for syncing files could be improved
• Would be nice if there was an easy way to use media from WP Engine host to save on space for larger sites
• 1 click login doesn't always work as expected if SSL in place.

Incentivized

Super easy to use the only thing that might need some improvement is the interface for syncing files. It's intuitive for push/pulling down from WP Engine and Flywheel environments but can sometimes disconnect and require re authentication. Also currently sometimes it can be difficult to tell proper account name you are pulling from bug that's a known bug that's being worked on

Incentivized

While Docker is powerful, setup is more complicated and is less consistent. Local minimizes friction and does what it needs to do with out extra complication that can sometimes come with using Docker or other platforms.

Incentivized

• Save hours of onboarding time for development
• Consistent environments across the time minimize unexpected issues
• Integrated error reporting makes it easy to track down issues

Incentivized