Magento 2.3.0 Installation Notes

Magento 2.3.0 Installation Notes

Magento Installation Requirements

Magento can be installed on a Dedicated, Virtual, Cloud or CloudNX server with at least 4GB of RAM.

Apache/2.4.33 (Win32) OpenSSL/1.1.0h PHP/7.2.7


Dev Environment:

Apache/2.4.33 (Win32) OpenSSL/1.1.0h PHP/7.2.7

Zend Engine v3.2.0

Database server

  • Server: 127.0.0.1 via TCP/IP
  • Server type: MariaDB
  • Server connection: SSL is not being used 
  • Server version: 10.1.34-MariaDB – mariadb.org binary distribution
  • Protocol version: 10
  • User: root@localhost
  • Server charset: UTF-8 Unicode (utf8)

Web server

  • Apache/2.4.33 (Win32) OpenSSL/1.1.0h PHP/7.2.7
  • Database client version: libmysql – mysqlnd 5.0.12-dev – 20150407 – $Id: 38fea24f2847fa7519001be390c98ae0acafe387 $
  • PHP extension: mysqli curl mbstring
  • PHP version: 7.2.7

phpMyAdmin

  • Version information: 4.8.2

Magento also requires the following PHP extensions to be enabled on your server:

  • PDO_MySQL
  • simplexml
  • mcrypt
  • hash
  • GD
  • DOM
  • iconv
  • curl
  • SOAP (if Web services API is to be used)
  • Safe mode off
  • Memory limit no less than 256Mb (preferably 512)

Installation flow diagram

Software Development Life Cycle (VG_Magernto_2)

DTAP which is short for Development, Testing, Acceptance, and Production outlines an approach to testing and deploying software as part of the SDLC.

When implementing SDL Web, to manage the development process and clearly separate the project implementation phases, SDL recommends using a Development, Test, Acceptance and Production infrastructure (DTAP). DTAP lets different users manage different types of content on different Content Manager Servers: the creation and management of content is distributed over several machines to prevent different types of content from getting in each other’s way. You then use Content Porter or a custom client to transfer data from one SDL Web environment to another.

Development Server

Developers develop code solely on the development machine to create all the Building Blocks content authors require in order to create content for Web sites, for example Schemas and Templates. They may also create other reusable data that is not code but that is not managed by content authors, such as a Multimedia Component that contains the company logo, or a Component that contains a standard disclaimer, but essentially the machine does not contain actual content. When developers have finished creating their code, Content Porter or a custom client is used to export the code to produce a set of intermediate files.

Test Server

Testers import the intermediate files produced by developers to the test machine where they test the code against test data (technical testing). Test data may be selectively taken from the production server, produced manually or generated randomly.

Acceptance Server

When tested, you use Content Porter or a custom client to import code (using the intermediate files) to an acceptance machine where it is subject to real use. The intermediate files are the same ones imported to the test machine. The acceptance machine contains real data and contains as perfect a copy of the actual production machine content as possible. Authors and editors use this machine to evaluate new code (functional testing).

Production Server

When accepted, you import code to the production machine, again using the exact same intermediate files. After verifying that the system works with the new code, authors and editors use this machine to create actual content for the Web site. The acceptance and production machines are functionally identical.

Magento 2.3.0 CE

Magento 2:

Downloaded the latest version of Magento 2 (2.3.0) version and installed on localhost server.

Magento website theme:

Solwin Freego White 2.3.x theme

Magento Test Website added Extensions:

Ext Name Link  
Social Login https://www.mageplaza.com/magento-2-social-login-extension/ DONE
Social Shares https://www.mageplaza.com/magento-2-social-share/ DONE
Newsletter Popup https://www.mageplaza.com/magento-2-newsletter-popup/ DONE
Google Maps https://www.mageplaza.com/magento-2-google-maps/ DONE
Tawk Chat https://www.tawk.to/knowledgebase/plugins-and-modules/magento-2-integration/ DONE
LocalHost Test Site (DEV) Test Live Server (UAT) Main Server (Prod)
Installation AWS Configuration  
Configuration LAMP  
Freego Slowin Theme Magento2 Installations  
Mageplaza Exts    
Theme Customizations    
Custom CSS style Module    
     

Test Coverage

The procedure covers the following aspects of testing the store as a first-time guest user.

  • Testing with both desktop and mobile devices.
  • Visiting the homepage.
  • Adding a product to the cart from a “featured products” or “hot sellers” block.
  • Navigating to a category page and adding a product on it to the cart.
  • Searching for a product and adding a product to the cart from the search results.
  • Adding a product to the cart from a product details page, including at least one product with options.
  • Viewing the minicart and using its features.
  • Viewing the shopping cart and using its features.
  • Checking out.
  • Reviewing the order confirmation.
  • Opening an account.
  • Using account page features.
  • Viewing the 404 page.

https://www.softwaretestingclass.com/web-application-testing/

Magento Installation – Test server for compatibility with Magento

https://www.magestore.com/magento-installation/test-server-for-compatibility-with-magento

Magento 2 Hosting – Web hosting

https://www.mageplaza.com/blog/magento-2-web-hosting.html

Mageplus server for Magento2

https://www.aspirationhosting.com/MagePlus_Pricing

Important notes related to Virtual Server and hosting

https://community.bitnami.com/t/which-is-the-best-economical-hosting-for-magento-cloud-or-dedicated-server-or-vps/29857/6



Leave a Reply

Your email address will not be published.

*
*
*