Instructions for how to install Homebrew itself can be found on the official Homebrew website. We'll look at how to set up a local development environment using these and, as usual, we’ll try to cover the “why” as well as the “what” in addition to just presenting the configuration, we'll go over the purpose of each directive and command. Instead of using the built-in versions, we’ll install Apache and PHP using Homebrew. Finally, running php -v to check the version of the built-in PHP gives a warning message stating that PHP will be removed from future versions of macOS - in fact, in the upcoming macOS Monterey, PHP seems to be gone. I’ve had problems where OS updates have overwritten my configuration for the built-in Apache server. We don’t have control over the exact versions used, and the version available might not be up to date. However, there are a few drawbacks to this approach. MacOS comes with built-in versions of Apache and PHP, and we could easily use those.
In this post, we’ll go through how to set up Apache and PHP, using versions installed using the Homebrew package manager for macOS. However, a convenient and simple solution is to just set up Apache running natively in macOS - no wrappers, no virtual machines, no containerization. There are also solutions with graphical user interfaces like MAMP. We could use Docker to run Apache in a container.
We could set up Apache in a virtual machine, perhaps controlled using Vagrant. On macOS, which is what we use, for the most part, there are quite a few options. This means setting up a development environment with Apache. While this doesn’t mean we have to use Apache to run the sites locally, using a similar stack for development and production is generally a good idea. At Tower, we use Apache to host websites like our learning platform, our blog, and our main product site.
0 kommentar(er)
