Table of Contents for
Magento 2 - Build World-Class online stores

Version ebook / Retour

Cover image for bash Cookbook, 2nd Edition Magento 2 - Build World-Class online stores by Jonathan Bownds Published by Packt Publishing, 2017
  1. Cover
  2. Table of Contents
  3. Magento 2 - Build World-Class online stores
  4. Magento 2 - Build World-Class online stores
  5. Credits
  6. Preface
  7. 1. Module 1
  8. 1. Magento Fundamentals
  9. XAMPP installation
  10. Magento
  11. Summary
  12. 2. Magento 2.0 Features
  13. An introduction to the Magento order management system
  14. Magento 2.0 command-line configuration
  15. The command-line utility
  16. Summary
  17. 3. Working with Search Engine Optimization
  18. Store configuration
  19. SEO and searching
  20. SEO catalog configuration
  21. Google Analytics tracking code
  22. Optimizing Magento pages
  23. Summary
  24. 4. Magento 2.0 Theme Development – the Developers' Holy Grail
  25. Magento 2.0 theme structure
  26. The Magento Luma theme
  27. Magento theme inheritance
  28. CMS blocks and pages
  29. Custom variables
  30. Creating a basic Magento 2.0 theme
  31. Summary
  32. 5. Creating a Responsive Magento 2.0 Theme
  33. Composer – the PHP dependency manager
  34. Building the CompStore theme
  35. CSS preprocessing with LESS
  36. Applying new CSS to the CompStore theme
  37. Creating the CompStore logo
  38. Applying the theme
  39. Creating CompStore content
  40. Customizing Magento 2.0 templates
  41. Summary
  42. 6. Write Magento 2.0 Extensions – a Great Place to Go
  43. Using the Zend framework
  44. Magento 2.0 extension structure
  45. Developing your first Magento extension
  46. The Twitter REST API
  47. The TweetsAbout module structure
  48. Using TwitterOAuth to authenticate our extension
  49. Developing the module
  50. Summary
  51. 7. Go Mobile with Magento 2.0!
  52. Adjusting the CompStore theme for mobile devices
  53. The Magento 2.0 responsive design
  54. The Magento UI
  55. Implementing a new CSS mixin media query
  56. Adjusting tweets about extensions for mobile devices
  57. Summary
  58. 8. Speeding up Your Magento 2.0
  59. Indexing and caching Magento
  60. Indexing and re-indexing data
  61. The Magento cron job
  62. Caching
  63. Fine-tuning the Magento hosting server
  64. Selecting the right Magento hosting service
  65. Apache web server deflation
  66. Enabling the expires header
  67. Minifying scripts
  68. Summary
  69. 9. Improving Your Magento Skills
  70. Magento knowledge center
  71. Improving your Magento skills
  72. Summary
  73. 2. Module 2
  74. 1. Magento 2 System Tools
  75. Installing Magento 2 sample data via GUI
  76. Installing Magento 2 sample data via the command line
  77. Managing Magento 2 indexes via the command line
  78. Managing Magento 2 cache via the command line
  79. Managing Magento 2 backup via the command line
  80. Managing Magento 2 set mode (MAGE_MODE)
  81. Transferring your Magento 1 database to Magento 2
  82. 2. Enabling Performance in Magento 2
  83. Configuring Redis for backend cache
  84. Configuring Memcached for session caching
  85. Configuring Varnish as the Full Page Cache
  86. Configuring Magento 2 with CloudFlare
  87. Configuring optimized images in Magento 2
  88. Configuring Magento 2 with HTTP/2
  89. Configuring Magento 2 performance testing
  90. 3. Creating Catalogs and Categories
  91. Create a Root Catalog
  92. Create subcategories
  93. Manage attribute sets
  94. Create products
  95. Manage products in a catalog grid
  96. 4. Managing Your Store
  97. Creating shipping and tax rules
  98. Managing customer groups
  99. Configuring inventories
  100. Configuring currency rates
  101. Managing advanced pricing
  102. 5. Creating Magento 2 Extensions – the Basics
  103. Initializing extension basics
  104. Working with database models
  105. Creating tables using setup scripts
  106. Creating a web route and controller to display data
  107. Creating system configuration fields
  108. Creating a backend data grid
  109. Creating a backend form to add/edit data
  110. 6. Creating Magento 2 Extensions – Advanced
  111. Using dependency injection to pass classes to your own class
  112. Modifying functions with the use of plugins – Interception
  113. Creating your own XML module configuration file
  114. Creating your own product type
  115. Working with service layers/contracts
  116. Creating a Magento CLI command option
  117. 3. Module 3
  118. 1. Planning for Magento
  119. Technical considerations
  120. Global-Website-Store methodology
  121. Planning for multiple stores
  122. Summary
  123. 2. Managing Products
  124. Managing products the customer focused way
  125. Creating products
  126. Managing inventory
  127. Pricing tools
  128. Autosettings
  129. Related products, up-sells, and cross-sells
  130. Importing products
  131. Summary
  132. 3. Designs and Themes
  133. The concept of theme inheritance
  134. Default installation of design packages and themes
  135. Installing third-party themes
  136. Inline translations
  137. Working with theme variants
  138. Customizing themes
  139. Customizing layouts
  140. Summary
  141. 4. Configuring to Sell
  142. Payment methods
  143. Shipping methods
  144. Managing taxes
  145. Transactional e-mails
  146. Summary
  147. 5. Managing Non-Product Content
  148. Summary
  149. 6. Marketing Tools
  150. Promotions
  151. Newsletters
  152. Using sitemaps
  153. Optimizing for search engines
  154. Summary
  155. 7. Extending Magento
  156. The new Magento module architecture
  157. Extending Magento functionality with Magento plugins
  158. Building your own extensions
  159. Summary
  160. 8. Optimizing Magento
  161. Indexing and caching
  162. Caching in Magento 2 – not just FPC
  163. Tuning your server for speed
  164. Summary
  165. 9. Advanced Techniques
  166. Version control
  167. Magento cron
  168. Backing up your database
  169. Upgrading Magento
  170. Summary
  171. 10. Pre-Launch Checklist
  172. System configurations
  173. Design configurations
  174. Search engine optimization
  175. Sales configurations
  176. Product configurations
  177. Maintenance configurations
  178. Summary
  179. Index

Configuring Redis for backend cache

Redis may be one of the best improvements since we used Memcache(d) or Alternative PHP Cache (APC). For the last couple of years, Redis is available in Magento 1 and has a big performance benefit.

What is Redis and why is it important for Magento? Well, Redis is not new; its initial release dates to the beginning of 2009—almost as young as Magento 1. Redis is a key-value storage database that stores the data in-memory of your web server. Besides this, the in-memory caches are fast and also have a persistence feature that is really important when a server reboots. All caches are not flushed during a reboot and are available in-memory when the web server is up again.

In the beginning of the Magento 1 area, we used Memcache(d) or APC, which worked very well but not as well as Redis. In Magento 1, Redis was used for a backend cache and session storage most of the time. Some websites also used it as a Full Page Cache (FPC) storage.

One other great advantage of Redis is that it has multiple database containers, one for the default cache and the other for the FPC. Although the Redis performance is better in a lot of cases, it is not the Holy Grail. There are drawbacks to its architecture.

Getting ready

For this recipe, we will use a Droplet created in Chapter 1, Magento 2 System Tools, at DigitalOcean, https://www.digitalocean.com/. We will be using NGINX, PHP-FPM, and a Composer-based setup, including sample data connected to a Redis server. No other prerequisites are required.

How to do it…

For the purpose of this recipe, let's assume that we need to create a Magento 2 Redis setup. The following steps will guide you through this:

  1. First, we need to install the Redis server and Redis PHP client before we can connect it to Magento. Follow the next step on the shell:
    cd /opt
    wget http://download.redis.io/releases/redis-3.0.5.tar.gz
    tar xzf redis-3.0.5.tar.gz
    cd redis-3.0.5
    make && make install
    

    Change the version number of the current one if needed.

  2. Go to the /opt/redis-3.0.5/utils directory and run the following script:
    ./install-server.sh
    
  3. Commit to the following questions: (Press Enter to all of them; the default is just fine.)
    Welcome to the redis service installer
    This script will help you easily set up a running redis server
    
    Please select the redis port for this instance: [6379]
    Selecting default: 6379
    Please select the redis config file name [/etc/redis/6379.conf]
    Selected default - /etc/redis/6379.conf
    Please select the redis log file name [/var/log/redis_6379.log]
    Selected default - /var/log/redis_6379.log
    Please select the data directory for this instance [/var/lib/redis/6379]
    Selected default - /var/lib/redis/6379
    Please select the redis executable path [/usr/local/bin/redis-server]
    Selected config:
    Port           : 6379
    Config file    : /etc/redis/6379.conf
    Log file       : /var/log/redis_6379.log
    Data dir       : /var/lib/redis/6379
    Executable     : /usr/local/bin/redis-server
    Cli Executable : /usr/local/bin/redis-cli
    Is this ok? Then press ENTER to go on or Ctrl-C to abort.
    Copied /tmp/6379.conf => /etc/init.d/redis_6379
    Installing service...
    Success!
    Starting Redis server...
    Installation successful!
    
  4. Now let's test our Redis server using the following command:
    redis-cli –version
    service redis_6379 status
    netstat –anp | grep redis
    

    As you can see, the Redis server is running under port 6379.

  5. The next important element is installing a PHP module that can communicate with the Redis server. We will use PHP Redis here (https://github.com/phpredis/phpredis).

    Use the following command to install PHP Redis:

    cd /opt
    git clone https://github.com/phpredis/phpredis.git
    cd phpredis
    phpize
    ./configure
    make && make install
    
  6. Now, we need to let PHP know there is a Redis extension available that we can use. Run the following command:
    echo "extension=redis.so" | sudo tee /etc/php5/mods-available/redis.ini
    

    Depending on whether you are using PHP 5 or PHP 7, you may want to change the PHP path.

  7. Now we need to link the Redis PHP extension to PHP-FPM and PHP CLI. Run the following commands:
    cd /
    ln -s /etc/php5/mods-available/redis.ini /etc/php5/fpm/conf.d/20-redis.ini
    ln -s /etc/php5/mods-available/redis.ini /etc/php5/cli/conf.d/20-redis.ini
    
  8. If everything is correct, we can restart the PHP-FPM server to activate the Redis PHP extension. Run the following command:
    service php5-fpm restart
    
  9. To make sure that the Redis PHP and Redis server are running together, we can use the following command:
    php -r "if (new Redis() == true){ echo \"\r\n OK \r\n\"; }"
    

    By default, creating a phpinfo.php page in the root directory in Magento 2 will not work. First, you need to create the phpinfo.php file in the /pub directory. Then, you need to change the NGINX configuration (nginx.conf.sample) from location ~ (index|get|static|report|404|503)\.php$ { to location ~ (index|get|static|report|404|503|phpinfo)\.php$ {, which is located at the bottom of the file. In Apache, we don't have an issue like this; it works by default.

    Tip

    Use phpinfo.php wisely on a production environment. Sharing this information on a production website is not advised and could expose your security risks.

  10. Congratulations, you just finished the Redis server and PHP Redis setup. Now let's continue with the Magento 2 part.
  11. Open the env.php file in Magento 2 located at /app/etc and add the following code at the top:
    How to do it…
  12. As you can see, we are using two databases—one for the default cache and one for page_cache (Full Page Cache). Now, save your file and remove any cache in /var/page_cache and /var/cache. Let's open up your browser and refresh your website.

    If everything is configured correctly in the env.php file, you should not get any errors and the ar/page_cache and var/cache directories should be empty.

  13. To check how many keys Redis received, we can run the following command from the shell:
    redis-cli
    

    On the prompt, continue with INFO; this will give you a list of the following details:

    How to do it…

    To close the Redis terminal, use exit.

  14. Congratulations, you just finished configuring the Redis server and PHP Redis with Magento 2.

How it works…

Let's recap and find out what we did throughout this recipe. In steps 1 through 13, we installed a Redis server and configured Magento 2 to store the backend cache.

In step 1, we installed Redis from source and compiled the code. This version is more stable than the default one available in Ubuntu. After compiling the code, we are able to use an install script to create a working setup running on port 6379.

After installing and testing the code in steps 3 and 4, we start installing the PHP Redis module. This code is pulled from GitHub and compiled from source.

In step 6, we created a redis.ini file, which is linked in step 7 with the correct PHP module directory. Before we can test it, we need to restart the PHP-FPM server and use a simple PHP command to test if everything is working fine.

In step 11, we added an additional piece of code to the env.php file, which will tell Magento 2 to store all of the cache in Redis as of now.

There's more…

If you are interested in monitoring your Redis server, the next step is interesting. Clone PHPRedMin (https://github.com/sasanrose/phpredmin) in your Magento 2 root directory, /var/www/html. Make sure to change the ownership to www-data for the owner and group.

Go to your /var/www/html/pub directory and create a symbolic link using the following command:

ln –s ../phpredmin/public phpredmin

Chown the ownership of the symbolic link with the following command:

chown -h www-data:www-data phpredmin

Go to to your NGINX configuration directory, /etc/nginx/conf.d, open the default.conf file, and including the following content below error_log:

location ~ ^/phpredmin/.+\.php {
  fastcgi_split_path_info ^(.+\.php)(/.+)$;

  set $fsn /index.php;
  if (-f $document_root$fastcgi_script_name) {
    set $fsn $fastcgi_script_name;
  }

  # php5-fpm
  fastcgi_pass fastcgi_backend;
  fastcgi_index  index.php;

  fastcgi_param  SCRIPT_FILENAME  $document_root$fsn;
  fastcgi_param  PATH_INFO  $fastcgi_path_info;
  fastcgi_param  PATH_TRANSLATED  $document_root$fsn;

  include fastcgi_params;
}

Now save and restart your NGINX server with service nginx restart.

Before we can continue, we need to add a cronjob rule to gather our Redis data and show it in PHPRedMin. Add the following rule to your crontab.

Open crontab using crontab –e:

* * * * * cd /var/www/html/pub/phpredmin && php index.php cron/index

Open your browser and surf to http://yourdomain.com/phpredmin, and press Stats in the top menu. Now you should see the following information:

There's more…

Tip

On a production site, you will want to add an IP block so that only you can gain access.