@@ -119,23 +123,23 @@ # Folder Organization -* **Now you'll need to organize the folder names, which is very important.** +- **Now you'll need to organize the folder names, which is very important** -* **Copy the ' wp-new-site ' folder and paste it in the same directory and it should create a new folder called ' wp-new-site - Copy '. This will leave the ' wp-new-site ' folder untouched so it can remain a template that you can copy/paste as many times as you want for any new site you want to launch.** +- **Copy the ' wp-new-site ' folder and paste it in the same directory and it should create a new folder called ' wp-new-site - Copy '. This will leave the ' wp-new-site ' folder untouched so it can remain a template that you can copy/paste as many times as you want for any new site you want to launch** -* **Rename the new folder you just created, ' wp-new-site - Copy ', to match your specific domain. Ex. ' wp-website-com '. You're keeping the 'wp-' part for easy filtering. You're changing the word 'new' to whatever your domain is. Then you're changing the word 'site' to whatever your domain extention is.** +- **Rename the new folder you just created, ' wp-new-site - Copy ', to match your specific domain. Ex. ' wp-website-com '. You're keeping the 'wp-' part for easy filtering. You're changing the word 'new' to whatever your domain is. Then you're changing the word 'site' to whatever your domain extention is** -* So here are a couple of examples: - * For 'jhammah.com', you would change 'wp-new-site' to 'wp-jhammah-com' - * For 'takedownthe.gov', you would change 'wp-new-site' to 'wp-takedownthe-gov' - * For 'dronework.pro', you would change 'wp-new-site' to 'wp-dronework-pro' +- So here are a couple of examples: + - For 'jhammah.com', you would change 'wp-new-site' to 'wp-jhammah-com' + - For 'takedownthe.gov', you would change 'wp-new-site' to 'wp-takedownthe-gov' + - For 'dronework.pro', you would change 'wp-new-site' to 'wp-dronework-pro' -* **For this tutorial, I'll be creating a site for the domain I own, scrapyardplays.com, which means I'll change 'wp-new-site' to 'wp-scrapyardplays-com'** +- **For this tutorial, I'll be creating a site for the domain I own, scrapyardplays.com, which means I'll change 'wp-new-site' to 'wp-scrapyardplays-com'** @@ -146,7 +150,17 @@ # Configuring .env file -* **This is the .env file. Here you will want to enter your cloudflare API token as well as the email address you log into cloudflare with. This .env file will create variables that you can reference in your Caddyfile.** +- **This is the .env file. Here you will want to change the default names of things to match your new site and folder naming structure** + +- **Rename the MYSQL Database** + +- **Rename the MYSQL User** + +- **Enter a strong MYSQL password** + +- **Enter a stronger MYSQL Root password** + +- **Rename the MYSQL Database Host**
+
@@ -162,11 +176,11 @@
# Configuring docker-compose.yml file
-* **Configuring docker-compose.yml file**
+- **Here is the docker-compose.yml file which contains all of the infor to create containers for your site**
-```yml
-code
-```
+- **Open the ' docker-compose.yml ' file and you'll neet to make some mass changes which is really easy with just about any text editor**
+
+- **You will replace all 17 occurrences of ' wp-new-site ' with your ' wp-website-com '. Most Text editors should be able to replace words in bulk. So for this tutorial, I'm replacing all 17 occurrences of ' wp-new-site ' with ' wp-scrapyardplays-com '**
@@ -178,6 +192,8 @@ code
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+- **Note that in the 'wordpress' container, we're not pulling an image. Instead we're referencing the 'Dockerfile' by adding the function 'build' and telling it that the Dockerfile should be in the same location as the .yml file by adding a period**
+
+- **If you open the Dockerfile, you'll see that it's first line is to pull the latest wordpress image. But then you'll notice the second line which are basic Linux update commands.**
+
+- **These lines are very important as they immediately update the core of the wordpress container's Linux environment upon container stopping and startings.**
+
+- **With the addition of these update lines, we'll be able to use the Nano text exitor in the console when we need to adjust any PHP code.**
+
+- **Next you'll be changing the port numbers. Each .yml file will be creating four containers for each website you want to launch**
+
+- **For each service inside of the .yml file, change all of the left-ports to something you have available**
+
+- **Only change the left-ports and leave the right-ports the same. Ex: database ####:3306, phpmyadmin ####:80, wordpress ####:80, redis ####:6379**
+
-
-
+- **Now under the ' redis ' container, change the REDIS_DATABASE number to match which site this is for you**
+
+- **If this is your first site, change it to ' 1 ' . If this is your second site, change it to ' 2 ', etc.**
+
+- **Docker will pull the images, build the containers, and install everything under it's unique stack name while giving each container a name similar to your website. Also it will attach these containers to the wordpress-network.**
+
+
+
+- **Once it's done, you can now open a browser and go to ' http://localhost:#### ' (replace the #### with whatever port you chose for your Wordpress service/container)**
+
+- **It should take you to the Wordpress setup page to finalize your install. Complete that install and then your locally hosted website will be live!**
+
# wp-config.php configuration
-**wp-config.php configuration**
+
+
+- **Enter this command and it will have you start editing the wp-config.php file: **
+
+```php
+nano wp-config.php
+```
+
+
+ 
+
# Caddyfile configuration
-**wp-config.php configuration**
+- **Caddyfile configuration**
-```ps1
-docker-compose up -d
-```
+
+
+# Redis Plugin
+
+- **Redis Plugin**
+
+
+ 
+ 
+ 
+
+
+
+
+# Final Test
+
+- **Final test**
+
+
+ Support the channel so I can make more tutorials!
If this tutorial helped you out, feel free to buy me a coffee!
