I use Local for all of my testing, especially as I am relatively new to WP and Bricks. I find it saves times when not creating from blue prints is to use export/import settings data files for the likes of Bricks, AT & ACSS etc to save time. Thanks for the skip-log-bin tip, I'd not seen that mentioned before, I'll see if its Windows only as I am not aware of huge log files on Mac. I do see a WP Memory warning most clean installs in the Bricks info tab so I add a "define( 'WP_MEMORY_LIMIT', '256M' );" line to the wp-config.php file. Not sure if this is a macOS thing. The biggest big time saver is my M2 Mac Studio! Keep up the great output and thanks for all the education and your hard work! 🙏
Why not use laragon? Fast free easy to update and multiple sites
Laragon can be installed only in Windows, whereas Local can be installed in Windows, Mac OS, and Linux.
I use Local for all of my testing, especially as I am relatively new to WP and Bricks. I find it saves times when not creating from blue prints is to use export/import settings data files for the likes of Bricks, AT & ACSS etc to save time.
Thanks for the skip-log-bin tip, I'd not seen that mentioned before, I'll see if its Windows only as I am not aware of huge log files on Mac. I do see a WP Memory warning most clean installs in the Bricks info tab so I add a "define( 'WP_MEMORY_LIMIT', '256M' );" line to the wp-config.php file. Not sure if this is a macOS thing.
The biggest big time saver is my M2 Mac Studio! Keep up the great output and thanks for all the education and your hard work! 🙏