#MAMP VS XAMPP FOR MAC PRO#
#MAMP VS XAMPP FOR MAC MAC#

Put all your website files in a folder вЂњmysiteвЂќ (for example) and put it in /Users/MyUsername/ like this /Users/MyUsername/mysite.

Press ESC, then :wq! to overwrite and close the file.

add your desired host name after local host:.

This opens a system file that contains the following line:.

#MAMP VS XAMPP FOR MAC MAC#

Open your console in mac and edit your hosts file like this:.

You might need to be logged in as an administrator to modify the hosts file. You need to be logged in as a Mac administrator to edit the files. However, if you donвЂ™t want to buy MAMP Pro, itвЂ™s quite simple to do it manually by editing two files.

#MAMP VS XAMPP FOR MAC PRO#

After a while, you should see something similar.The easiest way to set up virtual hosts in MAMP is to use the commercial version of MAMP, which automates the process through the MAMP Pro console. What this command does is, it will look for docker-compose.yml by default, start and run our entire app. Open a terminal at the wordpress directory, then run: docker compose up Okay thatвЂ™s a lot of stuff, but we are ready to get our applications running.

Line 29, we set the volume of db_data to be empty initially, which is then used on Line 7 by the db service.

Line 26вЂ“28, remember that we set MYSQL_DATABASE, MYSQL_USER, and MYSQL_PASSWORD on Line 11вЂ“13 to be wordpress, Wordpress will be using these values to connect to the MySQL database.

Port 3306 is the default port that MySQL runs on. Remember that we set our database service name to be db on Line 5.

Line 24, WORDPRESS_DB_HOST is the host that we want Wordpress to connect.

This way, we can visit Wordpress at localhost:8000. So we are saying, when we go to port 8000 on your machine, it should be forwarded to port 80 inside the container. 80 is the default port that Wordpress runs on. DonвЂ™t worry, we will see this in action later. Whenever we add a new plugin/theme, we will see the plugin gets added to wp-content/plugins in our current directory.

Line 19, we map the current directory(where docker-compose.yml is located) to /var/We are telling Wordpress to store its data to our current directory.

Line 18, use the latest version of Wordpress.

This way, we can make sure db, which is MySQL is ready before Wordpress starts to run.

In this case, db will run before wordpress on start up, and wordpress will exit first before db on exit. Line 16, depends_on allows us to control the sequence of services running.

Line 15, we define the second service we want to have, which is wordpress.

Scroll down to the Environment Variables section. You can see all the available environment variables for MySQL here.

Line 9вЂ“13, we set the required environment variables for MySQL, we set everything to wordpress.

Whenever db container stops running, it will always restart to keep the application alive. So which means, whenever MySQL writes its data files, it will instead write those data to db_data.

var/lib/mysql is the default location that MySQL will write its data file. Here we are mapping a volume called db_data to var/lib/mysql. So we want a persistent storage to store our data.

Line 6вЂ“7, we want the data in the DB to persist, if the container running our MySQL is restarted, the data within the container will be lost.

So, what we are saying here is, use mysql:5.7 to be the blueprint for db service. Think of an image is like a blueprint for your application, or a recipe for the cake you want to make.

Line 5, we define the image of db to be mysql:5.7.

Line 4, db is the name we use to define the first service we want to use.

Line 3, services is where we can define what images we want to use.

Line 1, we define we want to use Docker Compose version 3.9.

LetвЂ™s look at what the content of docker-compose.yml line by line.

Mamp vs xampp for mac