11/9/2023 0 Comments Mamp install composer![]() Valet+ is a fork by weprovide, which adds some useful features, like XDebug support, easily switching between PHP versions or Mailhog. It was initially developed by & for Laravel, but it’s perfectly suited for WordPress Development as well. Laravel Valet is a minimalist development environment for macOS. Vhosts – contains the actual directories for each of the sites I’m working on Scripts – contains all my dev scripts, like the ones to install and migrate live servers to local and stuff like that. Not that it really matters – you could structure your setup completely different than mine and it should work exactly the same – but for the sake of documentation, here’s how I structure my Development directories: Custom Migration & Installation Scripts. ![]() valet+ – a fork of Laravel Valet (needed a bit of a workaround to get it running, see below).macOS Monterey 12.1 (on M1 Apple Silicon).I want to use Mailhog to catch all mails from local installations.I want to be able to switch between php versions easily, bonus points if this could be defined per site, but I can live with a global switch.I want the ability to check out some of the plugins/themes from our git repos, instead of copying them from the live site.I want to be able to install WordPress plugins and themes with the same easy install script.I want to be able to install a new site quickly without much setup, and this should be scriptable from the command line.I want to be able to install and migrate (or just migrate if already installed) the current state of a live site, fast!.Most of the sites I’m working with are basic WordPress installs and quite similar to each other I don’t want to have to do all sorts of configurations for each site I install.I have my sites stored in one place ( ~/Development/vhosts/.).Here’s what I ended up with, at least for now. But last week, I was setting up my new MacBook Pro, and I thought there will never be a better time to give it a shot and see what I can optimize.Īfter reading through some of the docs and especially after reading this article by Jonathan Bossenger, I figured that while all of the solutions have their own pros and cons, Laravel Valet sounds like it fits my workflow the best. I never really took the time to finally look into all of them, and just kept everything as it was, still using MAMP. While researching, I stumbled across several different solutions, from the “ do-everything-yourself and set up *everything* manually” to docker-based, to varying vagrant vagrants or Laravel Valet. While MAMP is a comparably “easy” solution to setup sites, which works quite well, it has some limits – especially when you want to automate and script things. This became apparent, when we were looking for ways to streamline and automate some of our maintenance workflows. During this time, my requirements changed quite a bit compared to when I started. For the better part of the last 10 years or so, I was using MAMP (or later MAMP Pro) for my local development workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |