{"id":186,"date":"2017-12-17T11:48:02","date_gmt":"2017-12-17T11:48:02","guid":{"rendered":"https:\/\/learningcurve.xyz\/?p=186"},"modified":"2017-12-19T04:50:11","modified_gmt":"2017-12-19T04:50:11","slug":"alibaba-cloud-4-install-wordpress","status":"publish","type":"post","link":"https:\/\/learningcurve.xyz\/?p=186","title":{"rendered":"Alibaba Cloud 4 – Install WordPress"},"content":{"rendered":"

So here we are… The final part of our series, our Alibaba Ubuntu 16.04 ECS instance<\/a> is ready, we have NGINX, MariaDB, and PHP7<\/a> completing our stack. Our domain is configured and our site is protected with a Let’s Encrypt SSL certificate<\/a>. We are all ready to install WordPress, happy days!<\/p>\n

Completing the previous tutorials is a prerequisite for this one, so if you haven’t completed them yet, then follow the links above and come back here when you’re done.<\/p>\n

I would also be remiss to not point out, again, that most everything in this tutorial will work on most cloud providers.<\/p>\n

Step 1. Configure NGINX for WordPress<\/h2>\n

The First thing we need to do is make some slight modifications to our NGINX server blocks. Open the default NGINX configuration file with sudo<\/span> privileges:<\/p>\n

$ sudo nano \/etc\/nginx\/sites-available\/default\r\n<\/pre>\n
Within the server block we need to add some locations blocks.<\/p>\n
Turn off logging requests for  \/favicon.ico<\/span> and  \/robots.txt<\/span>. Then use a regular expression to match requests for static files, then turn logging off for these requests too, and mark them as highly cacheable since they are generally expensive resources to serve. If you have any other static files you want to cache, add them here too:<\/p>\n
server {\r\n    . . .\r\n\r\n    location = \/favicon.ico { log_not_found off; access_log off; }\r\n    location = \/robots.txt { log_not_found off; access_log off; allow all; }\r\n    location ~* \\.(css|gif|ico|jpeg|jpg|js|png)$ {\r\n        expires max;\r\n        log_not_found off;\r\n    }\r\n    . . .\r\n}\r\n<\/pre>\n
We also need to make some adjustments inside the  location \/<\/span> block.<\/p>\n
Comment out the  try_files<\/span> list line, where it returns a 404 error as a default option, and add code that passes control to the  index.php <\/span> file with the request argument instead:<\/p>\n
server {\r\n    . . .\r\n\t\r\n    location \/ {\r\n        #try_files $uri $uri\/ =404;\r\n        try_files $uri $uri\/ \/index.php$is_args$args;\r\n    }\r\n\t\r\n    . . .\r\n}\r\n<\/pre>\n
When you are finished your NGINX configuration file should look like the following:<\/p>\n
\"\"
Adjust NGINX configuration file for WordPress<\/figcaption><\/figure>\n
Make sure to check for syntax errors:<\/p>\n
$ sudo nginx -t\r\n<\/pre>\n
If there are none, reload NGINX:<\/p>\n
sudo systemctl reload nginx\r\n<\/pre>\n
Step 2. Install PHP Extensions most commonly used with WordPress<\/h2>\n
Previously we only installed the minimum PHP extensions required to get PHP to communicate with MariaDB and NGINX. However WordPress and its myriad ecosystem of plugins often leverage additional PHP extensions for increased functionality. We will install some of the most popular ones next.<\/p>\n
This step is optional, you could install these as and when you need them, but since we are already tweaking the LEMP stack for WordPress, why not do these now?<\/p>\n
First update your package repository index, and then install the chosen extensions by entering:<\/p>\n
$ sudo apt-get update\r\n$ sudo apt-get install php-curl php-gd php-mbstring php-mcrypt php-xml php-xmlrpc\r\n<\/pre>\n
Once they are finished installing, we need to restart the PHP-FPM process so these new features can be leveraged:<\/p>\n
sudo systemctl restart php7.0-fpm\r\n<\/pre>\n
Now PHP and NGINX are ready, we just need to add our Database with MariaDB and we can move on to WordPress.<\/p>\n
Step 3. Create a MySQL Database and User for WordPress<\/h2>\n
WordPress needs a MySQL Database to store site and user information. In the previous tutorial we installedd MariaDB as a drop in, more performant, replacement for MySQL.<\/p>\n
Now we need to use MariaDB to create the Database and User for WordPress to use.<\/p>\n
Log in to MariaDB, with root privileges, using the following  mysql<\/span> command:<\/p>\n
$ sudo mysql -u root -p\r\n<\/pre>\n
As usual, you will need to enter your superuser password before you can progress.<\/p>\n
Now create a Database for WordPress. Name it appropriately, for this tutorial I will be sticking with  wordpress<\/span> as my database name:<\/p>\n
MariaDB [(none)]> CREATE DATABASE wordpress<\/span> DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;\r\n<\/pre>\n
Next we need to create the user for this database. This user will be exclusive to our new database. I’m just going to use the same username as I have for my superuser, to keep things simple. You should choose whatever username you think is appropriate. I am also using a simple password for the benefit of the tutorial, but yours should be much more secure:<\/p>\n
MariaDB [(none)]> GRANT ALL ON wordpress<\/span>.* TO 'new_user<\/span>'@'localhost' IDENTIFIED BY 'new_users_password<\/span>';\r\n<\/pre>\n
Now we have the necessary Database and User account, all we have to do is flush the privileges so that MariaDB knows about the changes we’ve made. Then exit MariaDB:<\/p>\n
MariaDB [(none)]> FLUSH PRIVILEGES;\r\nMariaDB [(none)]> EXIT;\r\n<\/pre>\n
If you have followed along exactly, then your terminal should look like this:<\/p>\n
\"\"
Create a MariaDB Database and User for WordPress<\/figcaption><\/figure>\n
Step 4. Configure root directory ownerships<\/h2>\n
We will be setting up WordPress in the  \/var\/www\/html<\/span> directory, as set up in our NGINX configuration file server block. Change directory to this directory:<\/p>\n
$ cd \/var\/www\/html\r\n<\/pre>\n
If we try to import the WordPress files in this directory immediately, then we will receive a permissions error. That is because this directory currently belongs to  root<\/span> user in the  root<\/span> group.<\/p>\n
You can verify this by entering the following command to show the owner:<\/p>\n
$ ls -l\r\n<\/pre>\n
Your terminal will display the file and directory permissions, owner, date, time, and contents. You should see  root<\/span>  root<\/span> in the output.<\/p>\n
We will need to change the owner of the directory and the group the directory belongs to, in order to allow us to write the files we need within.<\/p>\n
First, with root privileges, add your superuser to the  www-data<\/span> usergroup, this is the NGINX server’s usergroup. In my case that is  new_user<\/span>:<\/p>\n
$ sudo usermod -aG www-data new_user<\/span>\r\n<\/pre>\n
Next, change the ownership of the  \/var\/www\/html<\/span> directory to your superuser and the  www-data<\/span> usergroup. In the case of my  new_user<\/span> that would be the following command:<\/p>\n
$ sudo chown -R new_user<\/span>:www-data \/var\/www\/html\r\n<\/pre>\n
Once this is done you can check the ownership of the directory again with the same command as previously:<\/p>\n
$ ls -l\r\n<\/pre>\n
Now the terminal should show the directory as belonging to your superuser and the  www-data<\/span> usergroup. If everything has been completed correctly, your terminal should look like the following:<\/p>\n
\"\"
Change ownership of the directory for WordPress<\/figcaption><\/figure>\n
We will be revisiting this directory and its ownership once we have installed WordPress, as it currently stands we won’t be able to install themes and plugins once WordPress is up and running. We can do that later.<\/p>\n
Install WordPress (Huzzah!!!)<\/h2>\n
Wait… you have a decision to make. This tutorial is going to show you two ways to install WordPress.<\/p>\n
The first is the original way, using  curl<\/span> and editing config files using nano etc. It is trusty and reliable method, and worth going through.<\/p>\n
The second is using WP CLI<\/a>, the awesome command line interface for WordPress, if you haven’t used it before then this is your chance to start. It’s awesome, and, once you get used to it, you can use it to manage all your WordPress sites with a workflow that offers such increased speed and efficiencies that you will never look back.<\/p>\n
Step 5. Install WordPress using CURL<\/h2>\n
Step 5a. Download WordPress<\/h3>\n
Change into a writable directory, yes I know we just took ownership of the WordPress destination directory, but this is just to be safe:<\/p>\n
$ cd \/tmp\r\n<\/pre>\n
Now use  curl<\/span> to download the compressed release with the following command:<\/p>\n
$ curl -O https:\/\/wordpress.org\/latest.tar.gz\r\n<\/pre>\n
Then extract the compressed file to create the WordPress directory and structure:<\/p>\n
$ tar xzvf latest.tar.gz\r\n<\/pre>\n
Next we need to change the  wp-config-sample.php<\/span> file into the  wp-config.php<\/span> filename needed by wordpress, use the copy command like so:<\/p>\n
$ cp \/tmp\/wordpress\/wp-config-sample.php \/tmp\/wordpress\/wp-config.php\r\n<\/pre>\n
We also need to create the  upgrade<\/span> directory needed by WordPress, so that it won’t run into permissino problems later when it tries to do this on it’s own:<\/p>\n
$ mkdir \/tmp\/wordpress\/wp-content\/upgrade\r\n<\/pre>\n
Okay, now we have a correctly configured and structured WordPress directory in the  \/tmp<\/span> directory, we can copy its entire contents into our html root directory. We will use the  -a<\/span> flag to maintain permissions. Notice the  .<\/span> period at the end of our source directory, this indicates that everything in the directory should be copied, including hidden files:<\/p>\n
$ sudo cp -a \/tmp\/wordpress\/. \/var\/www\/html\r\n<\/pre>\n
Step 5b. Set up the WordPress Configuration File<\/h3>\n
We need to configure some settings in the  wp-config.php<\/span> file so WordPress can talk to our database, and also to secure the installation.<\/p>\n
Open the configuration file:<\/p>\n
$ nano \/var\/www\/html\/wp-config.php\r\n<\/pre>\n
Enter the settings for the database we created with MariaDB earlier. You will need to correctly enter the name of the database, the database user, database user password and localhost, from earlier:<\/p>\n
. . .\r\n\r\ndefine('DB_NAME', 'wordpress<\/span>');\r\n\r\n\/** MySQL database username *\/\r\ndefine('DB_USER', 'new_user<\/span>');\r\n\r\n\/** MySQL database password *\/\r\ndefine('DB_PASSWORD', 'new_users_password<\/span>');\r\n\r\n\/** MySQL hostname *\/\r\ndefine('DB_HOST', 'localhost<\/span>');\r\n\r\n. . .\r\n<\/pre>\n
Close the file and save it.<\/p>\n
In my case, my  wp-config.php<\/span> now looks like the following, yours should be similar:<\/p>\n
\"\"
Add your Database settings to wp-config.php<\/figcaption><\/figure>\n
The  wp-config.php<\/span> file will also contain a section for secure ‘salt’ keys. It will look like this:<\/p>\n
. . .\r\n\r\ndefine('AUTH_KEY',         'put your unique phrase here');\r\ndefine('SECURE_AUTH_KEY',  'put your unique phrase here');\r\ndefine('LOGGED_IN_KEY',    'put your unique phrase here');\r\ndefine('NONCE_KEY',        'put your unique phrase here');\r\ndefine('AUTH_SALT',        'put your unique phrase here');\r\ndefine('SECURE_AUTH_SALT', 'put your unique phrase here');\r\ndefine('LOGGED_IN_SALT',   'put your unique phrase here');\r\ndefine('NONCE_SALT',       'put your unique phrase here');\r\n\r\n. . .\r\n<\/pre>\n
You will need to replace these keys with secure key values. We can get them from the WordPress secret key generator with the following command:<\/p>\n
$ curl -s https:\/\/api.wordpress.org\/secret-key\/1.1\/salt\/<\/pre>\n
Your terminal will display some unique values that look like the following:<\/p>\n
\"\"
Generate unique salt keys with the WordPress salt key generator<\/figcaption><\/figure>\n
Copy the salt keys.<\/p>\n
Open the wp-config.php<\/span> file, and paste these keys in place of the placeholder values:<\/p>\n
$ nano \/var\/www\/html\/wp-config.php\r\n<\/pre>\n
\"\"
Copy the secure salt keys into your wp-config.php<\/figcaption><\/figure>\n
Make sure you close and save the  wp-config.php<\/span> file.<\/p>\n
Now you’re ready to complete the installation.<\/p>\n
Step 5c. Complete the Famous WordPress 5 Minute Installation through the web interface<\/h3>\n
The server configuration is complete and teh WordPress directory and Configuration file is prepared, so now you can complete WordPress’s famous 5 minute installation by visiting your domain. Open your browser and navigate to your domain url:<\/p>\n
https:\/\/an-example-domain.com<\/span>\r\n<\/pre>\n
You will need to select your installation language, and then you’ll be prompted to complete your site and admin user information:<\/p>\n
\"\"
Complete the famous WordPress 5 minute installation<\/figcaption><\/figure>\n
Click install WordPress and you are done:<\/p>\n
\"\"
WordPress installed the Old Skool way!<\/figcaption><\/figure>\n
Your WordPress site should be up and running, and secured with an SSL.<\/p>\n
Permissions will need some adjusting to allow you to install and delete plugins and themes, and make other WordPress configuration changes, but we can do that later.<\/p>\n
Next we shall install WordPress using the fantastic WP CLI.<\/p>\n
Step 6. Installing WordPress using WP-CLI<\/h2>\n
Step 6a. Install WP-CLI<\/h3>\n
You can download the WP-CLI PHP Archive file  wp-cli.phar<\/span> using either  curl<\/span> or  wget<\/span> commands:<\/p>\n
$ curl -O https:\/\/raw.githubusercontent.com\/wp-cli\/builds\/gh-pages\/phar\/wp-cli.phar\r\n<\/pre>\n
or<\/p>\n
$ wget https:\/\/raw.githubusercontent.com\/wp-cli\/builds\/gh-pages\/phar\/wp-cli.phar\r\n<\/pre>\n
Next, you need to make the  wp-cli.phar<\/span> file executable, and move it to the  \/usr\/local\/bin<\/span> directory, so that it can be run directly:<\/p>\n
$ chmod +x wp-cli.phar\r\n$ sudo mv wp-cli.phar \/usr\/local\/bin\/wp\r\n<\/pre>\n
When these commands are completed, your terminal should look like the following:<\/p>\n
\"\"
Install WP-CLI<\/figcaption><\/figure>\n
You can check that it has been installed correctly by checking it’s info:<\/p>\n
$ wp --info\r\n<\/pre>\n
If you see something similar to the following, you can proceed:<\/p>\n
\"\"
Check wp –info to ensure WP-CLI installed correctly<\/figcaption><\/figure>\n
You will want to activate Bash Completion, this allows you to see all the available WP-CLI commands on the fly.<\/p>\n
First, download the bash script into your home directory:<\/p>\n
$ cd ~\/\r\n$ wget https:\/\/github.com\/wp-cli\/wp-cli\/raw\/master\/utils\/wp-completion.bash\r\n<\/pre>\n
Next open the  .bashrc<\/span> file:<\/p>\n
$ nano .bashrc\r\n<\/pre>\n
Add the folllwing line of code at the end of the  .bashrc<\/span> file:<\/p>\n
. . .\r\nsource \/home\/$USER\/wp-completion.bash\r\n<\/pre>\n
In the nano editor, the file should look like the following:<\/p>\n
\"\"
Edit the .bashrc file so the shell loads it every time you login<\/figcaption><\/figure>\n
Close and save the file, then run the following command to reload the bash profile:<\/p>\n
$ source ~\/.bashrc\r\n<\/pre>\n
Bash completion is now enabled, you can test this by typing wp theme<\/span>, including the trailing space, and then press tab twice. You will see a list of available commands with the wp theme<\/span> prompt.<\/p>\n
Your terminal should be showing:<\/p>\n
\"\"
Test Bash Completion<\/figcaption><\/figure>\n
Step 6b. Install WordPress using WP-CLI<\/h3>\n
Move to the  \/var\/www\/html <\/span> root directory for the site:<\/p>\n
$ cd \/var\/www\/html\r\n<\/pre>\n
This is where we will download the WordPress files. We took ownership of the directory previously, so we shouldn’t run into any errors while downloading the files and unpacking them:<\/p>\n
$ wp core download --locale=en_GB\r\n<\/pre>\n
You might think that I am downloading the British English version because I am British. Whilst that may be true, it’s also because there is currently a problem with the –locale=en_US<\/span> US English download.<\/p>\n
At the time of writing this tutorial downloading the US version throws an error during the unpack. I initially didn’t use a locale, which defaults to US English download, so this error had me running in circles until I found a github error log suggesting using a different language pack, and low and behold, it worked.<\/p>\n
Since I am British, this is okay, and it’s an opportunity for my US English speaking cousins to learn some proper English – win win!<\/p>\n
Now we need to create our wp-config file using our database values:<\/p>\n
$ wp core config --dbname=wordpress<\/span> --dbuser=new_user<\/span> --dbpass=new_users_password<\/span> --dbhost=localhost<\/span> --dbprefix=wp_<\/span>\r\n<\/pre>\n
Obviously you should use the database values that you created with MariaDB earlier, and not mine. Also notice how we don’t need to bother with the WordPress Salt Key Generator, that’s because WP-CLI does that for us – bonus.<\/p>\n
Finally, all we need to do is run the installation with the following command:<\/p>\n
$ wp core install --url=\"https:\/\/an-example-domain.com<\/span>\" --title=\"New Skool WP-CLI Installation<\/span>\" --admin_user=\"new_user<\/span>\" --admin_password=\"some_password<\/span>\" --admin_email=\"email@domain.com<\/span>\"\r\n<\/pre>\n
Again, make sure to use the values for your domain, admin username, password and email. Your terminal should look something like this:<\/p>\n
\"\"
Install WordPress with WP-CLI<\/figcaption><\/figure>\n
And that’s it…<\/p>\n
\"\"
WordPress is now installed – WP-CLI for the win!<\/figcaption><\/figure>\n
Seriously, how easy and fast was that? You can use WP-CLI to update WordPress core, plugins, themes, copy whole installations and databases, add admin users so you never get locked out, and so much more. But that is for another article…<\/p>\n
We aren’t finished yet though, remember those permissions?<\/p>\n
Step 7. Configure Root Directory Permissions for WordPress functions<\/h2>\n
Log in to your WordPress installation, go to the Plugins menu, and try to delete one of the preinstalled plugins. You should see a pop up box like the following:<\/p>\n
\"\"
WordPress needs FTP credentials to access the web server<\/figcaption><\/figure>\n
You could configure the SFTP account and credentials, that would work, or you could change the ownership of the WordPress root directory to the  www-data<\/span> NGINX server user and usergroup, using the following command:<\/p>\n
$ sudo chown www-data:www-data \/var\/www\/html\/\r\n<\/pre>\n
You can check that the  www-data<\/span> user and usergroup has taken ownership with the following command from within the domain root directory:<\/p>\n
$ ls -l\r\n<\/pre>\n
You should see the following output:<\/p>\n
\"\"
Set ownership of root directory to server user\/usergroup<\/figcaption><\/figure>\n
Now you should be able to install and delete plugins, themes, and uploads:<\/p>\n
\"\"
Now WordPress has access to the web server<\/figcaption><\/figure>\n
There you go, a fully functional WordPress site with…… hmmmm well, actually, I suppose it isn’t quite functional yet is it?<\/p>\n
One of the things with cloud hosting, with any provider, is that while you get a fast server you don’t get things like email functionality provided by the hosting provider.<\/p>\n
BONUS ROUND – Emails!<\/h2>\n
Firstly, for your general email, you should either pay for an email service such GApps, Rackspace, or one of the other providers, or you could roll your own email server.<\/p>\n
Email Server DNS records<\/h3>\n
I chose the latter for myself, and have a Mail-In-The-Box<\/a>\u00a0email server running on a Linode. It is quite a simple email server, there are more functional, and complicated, mail server solutions, but in general I direct most of my clients to use a professional hosted service and this is for my personal business use (I’m in China so the more common email solutions can have serious problems).<\/p>\n
To have my emails directed properly I added an  A<\/span> and  MX<\/span> record to the Alibaba DNS settings like so:<\/p>\n
\"\"
Add MX and A (Mail) records for an Email Server<\/figcaption><\/figure>\n
WordPress Transactional Emails<\/h2>\n
From a WordPress perspective though, what we really need to sort out, is our transactional emails. We need our WordPress installation to be able to send password reset emails, and the like.<\/p>\n
To do that, we could install Dovecot, PostFix etc etc on our server. But that would need maintaining and in my case I already have one email server to look after.<\/p>\n
So instead, let’s use an online hosted SMTP service, of which there are several. I personally use mailgun<\/a>\u00a0so this tutorial will demonstrate how to set their service up on your new install.<\/p>\n
Create a Mailgun account and add a domain<\/h3>\n
If you add a credit card to your account, mailgun has a free tier. On this tier you can send 10,000 emails a month, which is more than enough for anyone’s need of a free tier. If you are sending more emails than that a month, then you can surely afford to pay!<\/p>\n
Create a mailgun account at mailgun.com<\/a>, then\u00a0login and verify your email address.<\/p>\n
They have a free tier that doesn’t require you add a credit card, but is restricted to sending mail to at most 5 whitelisted email addresses. On the other hand, if you do add a credit card you can send up to 10,000 emails a month for free. Can’t say fairer than that!<\/p>\n
\"\"
Create a mailgun account and add a domain<\/figcaption><\/figure>\n
Mailgun needs you to add your domain to their system with a subdomain, they recommend using  mg.an-example-domain.com<\/span>, but I always use  mailgun.an-example-domain.com<\/span>, I prefer to be clear if a little verbose.<\/p>\n
Once you have added this domain, they will provide you with some DNS records:<\/p>\n
\"\"
Get the DNS records from your mailgun domain<\/figcaption><\/figure>\n
Go to your Alibaba ECS DNS records panel in the console, and add these records:<\/p>\n
\"\"
Add those records to your Alibaba Instance DNS records<\/figcaption><\/figure>\n
Once your DNS changes have propagated, your mailgun domain settings panel will show your domain as  Active<\/span>, and give you the settings you need to configure one of the many WordPress SMTP plugins:<\/p>\n
\"\"
After DNS record propagation your mailgun domain will be active<\/figcaption><\/figure>\n
Go back to your WordPress site, and choose an SMTP plugin. Mailgun has one, but at the moment there is a bug causing TLS connection errors, so instead I recommend Easy WP SMTP<\/a>:<\/p>\n
\"\"
Easy WP SMTP is an excellent choice for SMTP plugin<\/figcaption><\/figure>\n
Upon installation, goto the Easy WP SMTP plugins settings page and enter the credentials given to you on the mailgun domain settings page:<\/p>\n
\"\"
Enter your mailgun credentials in the plugin settings<\/figcaption><\/figure>\n
You can send a test mail from a test settings panel directly below the main settings:<\/p>\n
\"\"
Send a test email<\/figcaption><\/figure>\n
The plugin will display information from the test send, and whether it was succesful or not. If your settings are correct and everything is set up correctly you should see something like this:<\/p>\n
\"\"
A successful test<\/figcaption><\/figure>\n
You can also verify that the email has been sent successfully by checking the logs in your mailgun account:<\/p>\n
\"\"
Verify email sending success in the mailgun logs<\/figcaption><\/figure>\n
Now<\/em><\/strong> we are complete, we have a WordPress site running on a modern, performant LEMP stack, secured with an SSL, and with mailgun transactional emails, all on the Alibaba Cloud!<\/p>\n
If you have any questions, or noticed any mistakes or poor configuration practices, please leave a comment.<\/p>\n
Thanks<\/p>\n
Jeff<\/p>\n","protected":false},"excerpt":{"rendered":"
So here we are… The final part of our series, our Alibaba Ubuntu 16.04 ECS instance is ready, we have NGINX, MariaDB, and PHP7 completing our stack. Our domain is configured and our site is protected with a Let’s Encrypt SSL certificate. We are all ready to install WordPress, happy days! Completing the previous tutorials […]<\/p>\n","protected":false},"author":1,"featured_media":176,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,4],"tags":[],"_links":{"self":[{"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/posts\/186"}],"collection":[{"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=186"}],"version-history":[{"count":3,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/posts\/186\/revisions"}],"predecessor-version":[{"id":218,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/posts\/186\/revisions\/218"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=\/wp\/v2\/media\/176"}],"wp:attachment":[{"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=186"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=186"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/learningcurve.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=186"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}