{"id":1685,"date":"2018-12-10T08:36:27","date_gmt":"2018-12-09T23:36:27","guid":{"rendered":"https:\/\/n8finch2024.local\/?p=1685"},"modified":"2022-03-11T06:51:01","modified_gmt":"2022-03-10T21:51:01","slug":"using-local-by-flywheel-for-local-laravel-development","status":"publish","type":"post","link":"https:\/\/n8finch2024.local\/using-local-by-flywheel-for-local-laravel-development\/","title":{"rendered":"Using Local by Flywheel for Local Laravel Development"},"content":{"rendered":"\n

Note: This post has been updated to work with the new version of Local. I’ll try to keep things updated if the development environment changes in the future.<\/em> (last updated: March 2, 2022)<\/em><\/p>\n\n\n\n

While I mostly build with WordPress, I’m going to be working with a few projects coming up that will require a more custom application approach. So, I’m (most likely) going to use Laravel. Step one for any project is to get set up locally. If you’re like me, you like keeping things organized and try to keep things from getting redundant. <\/p>\n\n\n\n

For local development, this means using one solution as best I can to make getting setup and going on new projects as simple as possible. While I’ve used ScotchBox<\/strong><\/a>, VVV<\/a><\/strong> and WP Local Docker<\/strong><\/a> before, I’m using Local by Flywheel<\/a><\/strong> all the time now. It’s easy to get rolling, consistent for our team to use, and if you want to try out something like Laravel or Craft, you can easily sub those frameworks in. <\/p>\n\n\n\n

Here’s how I’m doing that with Laravel…<\/p>\n\n\n\n\n\n\n\n

\n