In this tutorial we will learn to install Apache, MySQL, PHP on macOS Catalina 10.15.
- Install Brew On Mac Catalina Update
- Install Brew On Mac Catalina
- Install Homebrew On Macos Catalina
- Install Brew On Mac Catalina Download
- Install Brew On Mac Catalina Os
- Brew Install Openssl Mac Catalina
About macOS Catalina
My catalina version is 10.15.2 (19C57) Home-brew version is. ShawnstationdeMacBook-Pro: shawnstation$ brew -version Homebrew 1.6.9 Homebrew/homebrew-core (git revision fab7d; last commit 2018-07-07). Open the Terminal app on your Mac. Install Homebrew via the instructions here: 3. Install Composer globally on your Mac with this command: brew install composer. If your computer doesn’t have a “/usr/local/bin” directory, create that first with this command: sudo mkdir -p /usr/local/bin. Homebrew (brew) is a free and open-source package manager that allows installing apps and software in macOS, depending on the user’s desire. It has been recommended for its simplicity and effectiveness in saving time and effort. Its famous description is “The missing package manager for macOS”. Brew install postgresql@9.5 9.5 in my case. Feel free to change the version according to your need once the installation is done, make an entry of that in /.bashprofile by running the below command.
Apple released macOS Catalina 10.15 on 7th October 2019 and it includes Apache and PHP. So, all we have to do is enable them. Then install MySQL and we are ready for development. So, lets get started.
Note! Support for 32 bit apps is removed in Catalina so, all your 32 bit applications will no longer work. Kindly upgrade your applications.
Apple has also made zsh as the default shell. You can learn more about it here.
To change the default shell check the tutorial How to change default shell to bash on macOS Catalina.
We will be using the pre-installed Apache and PHP and we will download and setup MySQL database.
If you are using macOS Mojave then check out this tutorial How to install Apache, MySQL, PHP on macOS Mojave 10.14
Lets go ahead and configure our LAMP stack development environment on macOS Catalina.
Apache
The new macOS Catalina comes with Apache pre-installed. All we have to do is switch it on.
Open Terminal using macOS Spotlight or go to /Applications/Utilities and open Terminal.
To check the version of Apache installed run the following command in the Terminal.
Note! macOS Catalina comes with Apache 2.4.41
To start Apache web server run the following command.
This command will start Apache server.
When you use sudo in the terminal then you will be prompted to enter your admin password to proceed.
If you want to stop the Apache server then run the following command.
And to restart Apache server run the following command.
After starting Apache server go ahead and test it by opening a browser like Safari or Chrome and visit http://localhost.
You will get to see the following output in your browser.
By default, the file is getting served from /Library/WebServer/Documents directory. We will change this is the following sections.
In case you don't get to see the above output then run the following command to check the error.
Document Root
This is the location in the computer file system from where the files are accessed when we visit the http://localhost in a browser.
Document Root is a directory where we put our website files.
On Mac we have two document root. One is at the system level and the other is at the user level.
System level document root
The system level document root in macOS Catalina is located in the following directory.
User level document root
For the user level we can create a directory called Sites in user directory. So, open Terminal and get ready to create the user level document root directory.
Creating Sites directory
Run the following command in the Terminal to switch to the user home directory.
Now, run the following command to create the Sites directory.
You can merge the above two commands into one by running the following command.
For me the user document root path is the following.
You will get a similar path for your Mac.
Creating username.conf file
Now, we will create a username.conf file to configure our document root.
Note! Replace the username with your username.
For example, my username is yusufshakeel so, my file is yusufshakeel.conf.
Type the whoami command in the terminal and it will tell you your username.
Open terminal and go to the following directory.
Now create the configuration file username.conf inside the users directory.
In the following example I am using vi editor. You can use other editors like vim or nano.
Press the i key to enter into INSERT mode and then type the following in the file.
Don't forget to replace YOUR_USER_NAME with your username.
Here is what I have written in my yusufshakeel.conf file.
Now, come out of the INSERT mode by pressing the Esc key. Now save the file and exit by typing the following :wq and then hit Enter.
The permission of this file should be the following.
You can change the permission by typing the following command.
Where, username is your username that you have set.
Configuring the httpd.conf file
Now we switch to apache2 directory by typing the following command in the Terminal.
Inside this directory we have the httpd.conf file.
As a good practice we will make a backup copy of the httpd.conf file by typing the following command.
Now open the httpd.conf file using vi and uncomment the following lines.
To uncomment the lines remove the # from the start of the line.
Uncomment the following line for User home directories.
Now change the DocumentRoot.
Find the following lines and comment them by adding # at the beginning of the line.
And add the following two lines below the commented lines.
Don't forget to replace YOUR_USERNAME with your username.
And set the AllowOverride None to AllowOverride All.
Your DocumentRoot should now look something like the following.
Now, come out of the INSERT mode by pressing the Esc key. And save and exit the file by typing :wq key and then Enter.
Configuring the httpd-userdir.conf file
Now, time to make some changes in the httpd-userdir.conf file.
In the terminal type the following command to go to the extra directory.
As a good practice create a backup copy of the httpd-userdir.conf file.
Now open the file using vi.
Enter into INSERT mode and uncomment the following line.
Now, come out of the INSERT mode and save the changes.
Now, check if everything is configured properly by typing the given command.
Now restart Apache using the following command.
PHP
macOS Catalina comes with PHP 7.3.8 pre-installed.
To check the version of PHP in the Terminal type the following command.
Now we go to the apache2 directory.
Next, we open the httpd.conf file.
Now, enter into INSERT mode and uncomment the following line to run PHP 7 by removing the # sign from the start of the line.
Now, save the changes and exit the file by typing :wq keys and hit Enter.
You can now restart Apache by running the following command.
Printing phpinfo
Create index.php file inside the Sites directory.
Now open the file in your favourite text editor or PHP IDE and write the following code.
Now, visit http://localhost and you will get to see a similar output.
Download MySQL community server
Head over to mysql.com website and download the latest version of the MySQL Community Server.
Install Brew On Mac Catalina Update
Download and run the installer and follow the steps to install MySQL database on your Mac.
Set the root password when prompted and note it down.
To run MySQL server open System Preferences and go to MySQL.
Click on the Start MySQL Server button to start the server.
You will be asked to enter your admin password. Enter the password and the MySQL server will start running.
Extra
To access your MySQL database tables you can either use phpMyAdmin, MySQL Workbench or Sequel Pro.
Alright, this brings us to the end of this tutorial. Hope this helped. Please share if you find this website useful. Have fun developing. See you in the next tutorial.
Additionally, SUMO provides native macOS application bundles for its graphical applications, so they can be added to the macOS dock. There is a separate brew cask that will copy these bundles to the Applications folder: brew cask install sumo-gui. 苹果公司在今天（2019.10.08）凌晨正式推送了 macOS Catalina（10.15)更新 ，新系统将诞生了18年的 iTune. You will need a macOS computer running High Sierra or higher with administrative access and an internet connection. Step 1 — Using the macOS Terminal. To access the command line interface on your Mac, you’ll use the Terminal application provided by macOS.
You can install cryptography with pip:
Hi, I am running MacOS X 10.14.3 (German Version) which I installed directly from the downloaded install ISO in the latest VMware Fusion. Now I get a notification form softwareupdate that there is an update available. Updated to reflect the release of macOS 10.5 Catalina Updated to add back PHP 5.6 and PHP 7.0 from and external deprecated keg Updated to reflect the latest release of PHP 7.3 and the removal of PHP 7.0 from Brew.
If this does not work please upgrade your pip first, as that is thesingle most common cause of installation problems.
Install Brew On Mac Catalina
Supported platforms¶
Currently we test cryptography on Python 3.6+ and PyPy3 7.3.1 on theseoperating systems.
- x86-64 & AArch64 CentOS 8.x
- x86-64 Fedora (latest)
- x86-64 macOS 10.15 Catalina
- x86-64 & AArch64 Ubuntu 18.04, 20.04
- x86-64 Ubuntu rolling
- x86-64 Debian Stretch (9.x), Buster (10.x), Bullseye (11.x), and Sid(unstable)
- x86-64 Alpine (latest)
- 32-bit and 64-bit Python on 64-bit Windows Server 2019
We test compiling with clang as well as gcc and use the followingOpenSSL releases:
OpenSSL1.1.0-latestOpenSSL1.1.1-latest
Building cryptography on Windows¶
The wheel package on Windows is a statically linked build (as of 0.5) so alldependencies are included. To install cryptography, you will typicallyjust run
If you prefer to compile it yourself you’ll need to have OpenSSL installed.You can compile OpenSSL yourself as well or use a binary distribution.Be sure to download the proper version for your architecture and Python(VC2015 is required for 3.6 and above). Wherever you place your copy of OpenSSLyou’ll need to set the LIB and INCLUDE environment variables to includethe proper locations. For example:
As of OpenSSL 1.1.0 the library names have changed from libeay32 andssleay32 to libcrypto and libssl (matching their names on all otherplatforms). cryptography links against the new 1.1.0 names by default. Ifyou need to compile cryptography against an older version then you mustset CRYPTOGRAPHY_WINDOWS_LINK_LEGACY_OPENSSL or else installation will fail.
You will also need to have Rust installed andavailable.
If you need to rebuild cryptography for any reason be sure to clear thelocal wheel cache.
Building cryptography on Linux¶
Note
If you are on RHEL/CentOS/Fedora/Debian/Ubuntu or another distributionderived from the preceding list, then you should upgrade pip andattempt to install cryptography again before following the instructionsto compile it below. These platforms will receive a binary wheel andrequire no compiler if you have an updated pip!
cryptography ships manylinux wheels (as of 2.0) so all dependenciesare included. For users on pip 19.0 or above running on a manylinux2010(or greater) compatible distribution (almost everything except Alpine) allyou should need to do is:
If you are on Alpine or just want to compile it yourself thencryptography requires a C compiler, a Rust compiler, headers for Python (ifyou’re not using pypy), and headers for the OpenSSL and libffi librariesavailable on your system.
On all Linux distributions you will need to have Rust installed andavailable.
Alpine¶
Warning
The Rust available by default in Alpine < 3.12 is older than the minimumsupported version. See the Rust installation instructions for information about installing a newer Rust.
If you get an error with openssl-dev you may have to use libressl-dev.
Debian/Ubuntu¶
Warning
The Rust available in current Debian stable and some Ubuntu versions isolder than the minimum supported version. Ubuntu 18.04 and 20.04 aresufficiently new, but otherwise please see theRust installation instructions for informationabout installing a newer Rust.
Fedora/RHEL 8/CentOS 8¶
Warning
For RHEL and CentOS you must be on version 8.3 or newer for the commandbelow to install a sufficiently new Rust. If your Rust is less than 1.41.0please see the Rust installation instructionsfor information about installing a newer Rust.
RHEL 7/CentOS 7¶
Warning
How To Install Brew On Catalina
You must install Rust using the Rust installation instructions. cryptography requires a Rust version newer thanwhat is provided in the distribution packages.
Building¶
You should now be able to build and install cryptography. To avoid gettingthe pre-built wheel on manylinux compatible distributions you’ll need touse --no-binary.
Using your own OpenSSL on Linux¶
Install Homebrew On Macos Catalina
Python links to OpenSSL for its own purposes and this can sometimes causeproblems when you wish to use a different version of OpenSSL with cryptography.If you want to use cryptography with your own build of OpenSSL you will need tomake sure that the build is configured correctly so that your version ofOpenSSL doesn’t conflict with Python’s.
The options you need to add allow the linker to identify every symbol correctlyeven when multiple versions of the library are linked into the same program. Ifyou are using your distribution’s source packages these will probably bepatched in for you already, otherwise you’ll need to use options something likethis when configuring OpenSSL:
Static Wheels¶
Cryptography ships statically-linked wheels for macOS, Windows, and Linux (viamanylinux). This allows compatible environments to use the most recentOpenSSL, regardless of what is shipped by default on those platforms. SomeLinux distributions (most notably Alpine) are not manylinux compatible sowe cannot distribute wheels for them.
However, you can build your own statically-linked wheels that will work on yourown systems. This will allow you to continue to use relatively old Linuxdistributions (such as LTS releases), while making sure you have the mostrecent OpenSSL available to your Python programs.
To do so, you should find yourself a machine that is as similar as possible toyour target environment (e.g. your production environment): for example, spinup a new cloud server running your target Linux distribution. On this machine,install the Cryptography dependencies as mentioned in Building cryptography on Linux.Please also make sure you have virtualenv installed: this should beavailable from your system package manager.
Then, paste the following into a shell script. You’ll need to populate theOPENSSL_VERSION variable. To do that, visit openssl.org and find thelatest non-FIPS release version number, then set the string appropriately. Forexample, for OpenSSL 1.0.2k, use OPENSSL_VERSION='1.0.2k'.
When this shell script is complete, you’ll find a collection of wheel files ina directory called wheelhouse. These wheels can be installed by asufficiently-recent version of pip. The Cryptography wheel in thisdirectory contains a statically-linked OpenSSL binding, which ensures that youhave access to the most-recent OpenSSL releases without corrupting your systemdependencies.
Building cryptography on macOS¶
Note
If installation gives a fatalerror:'openssl/aes.h'filenotfoundsee the FAQ for information about how to fix this issue.
The wheel package on macOS is a statically linked build (as of 1.0.1) so forusers with pip 8 or above you only need one step:
If you want to build cryptography yourself or are on an older macOS version,cryptography requires the presence of a C compiler, development headers, andthe proper libraries. On macOS much of this is provided by Apple’s Xcodedevelopment tools. To install the Xcode command line tools (on macOS 10.10+)open a terminal window and run:
Macos Catalina Brew Install
This will install a compiler (clang) along with (most of) the requireddevelopment headers.
You will also need to have Rust installed andavailable, which can be obtained from Homebrew,MacPorts, or directly from the Rust website.
Finally you need OpenSSL, which you can obtain from Homebrew or MacPorts.Cryptography does not support the OpenSSL/LibreSSL libraries Apple shipsin its base operating system.
To build cryptography and dynamically link it:
MacPorts:
You can also build cryptography statically:
MacPorts:
If you need to rebuild cryptography for any reason be sure to clear thelocal wheel cache.
Rust¶
Note
If you are on RHEL/CentOS/Fedora/Debian/Ubuntu or another distributionderived from the preceding list, then you should upgrade pip (ina virtual environment!) and attempt to install cryptography againbefore trying to install the Rust toolchain. These platforms will receivea binary wheel and require no compiler if you have an updated pip!
Building cryptography requires having a working Rust toolchain. The currentminimum supported Rust version is 1.41.0. This is newer than the Rust mostpackage managers ship, so users will likely need to install with theinstructions below.
Instructions for installing Rust can be found on the Rust Project’s website.We recommend installing Rust with rustup (as documented by the RustProject) in order to ensure you have a recent version.
Rust is only required when building cryptography, meaning that you mayinstall it for the duration of your pipinstall command and then remove itfrom a system. A Rust toolchain is not required to usecryptography. Indeployments such as docker, you may use a multi-stage Dockerfile whereyou install Rust during the build phase but do not install it in the runtimeimage. This is the same as the C compiler toolchain which is also required tobuild cryptography, but not afterwards.
- 1Notes
Some system emulations on Linux use KVM, a special emulation mode which claims to reach nearly native speed.KVM is mainly used for x86 (32 and 64 bit) emulation on x86 hosts running Linux. Should you want to run Qemu with KVM support on a G5, depending on your distribution, you might have to compile your own kernel with KVM support.
If your host's (your computer) architecture matches the guest's (QEMU) architecture and is running Mac OS 10.10 or higher, then you could speed up execution to near native speed using this option: -accel hvf
Installing QEMU using a package manager
Building QEMU for macOS
The system requirements are:
Install Brew On Mac Catalina Download
- One of the two most recent versions of macOS (currently Catalina or Big Sur)
- The clang compiler shipped with the version of Xcode for that OS X. GCC might also work, but we recommend clang
Additional build requirements are:
make (when installed through brew, make is installed as gmake, so use gmake)
After downloading the QEMU source code, double-click it to expand it.
Then configure and make QEMU. The target-list option is used to build only the machine or machines you want. If you don't specify it, all machines would be built. Probably not what you want.
Install Brew On Mac Catalina Os
This way doesn't require you to wait for the configure command to complete:
If your system has the 'say' command, you can use it to tell you when QEMU is done
You can use './configure --help' to see a full list of options.
Here are all the currently available machines:
- aarch64-softmmu
- alpha-softmmu
- arm-softmmu
- cris-softmmu
- i386-softmmu
- lm32-softmmu
- m68k-softmmu
- microblaze-softmmu
- microblazeel-softmmu
- mips-softmmu
- mips64-softmmu
- mips64el-softmmu
- mipsel-softmmu
- moxie-softmmu
- or32-softmmu
- ppc-softmmu
- ppc64-softmmu
- ppcemb-softmmu
- s390x-softmmu
- sh4-softmmu
- sh4eb-softmmu
- sparc-softmmu
- sparc64-softmmu
- tricore-softmmu
- unicore32-softmmu
- x86_64-softmmu
- xtensa-softmmu
- xtensaeb-softmmu
We recommend building QEMU with the -default compiler provided by Apple, for your version of Mac OS X (which will be 'clang'). The configure script will automatically pick this.
Errors on old compilers
Note: If after the configure step you see a message like this:
you may have to install your own version of gcc. You can build it from source (expect that to take several hours) or obtain third party binaries of gcc available from Homebrew or MacPorts.
You can have several versions of GCC on your system. To specify a certain version, use the --cc and --cxx options.
Build with LLVM/Clang 7
If you need to compile with newer versions of clang (to get f.i. AVX/AVX2 support), you can install llvm through e.g., brew.
Note that building for machines with CPUs supporting such extensions will exclude running your binary on earlier machines.
Compile with:
Contacts
If there are any issues with this web page, please let me know.