Using PrestaShop to Build an E-Commerce Website

Application Scenario

PrestaShop is a full-featured, cross-platform, and open source e-commerce platform written in the PHP programming language with support for the MySQL database management system. PrestaShop supports transactions using different currencies and almost all payment methods, such as Paypal. It is a good choice for you to build foreign trade websites. Supported By FlexusL, the PrestaShop application image uses Ubuntu 22.04 and is deployed using Docker. The Nginx, MySQL, phpMyAdmin, and Docker have been preconfigured in the image. This section describes how to use PrestaShop to build an e-commerce website.

Resource Planning and Costs

This practice uses the following resource planning as an example. You can adjust it as required.

Procedure

Step 1: Purchase a FlexusL Instance

1. Log in to the FlexusLconsole and click Buy FlexusL.
2. Specify required parameters for the FlexusL instance.
   

   Parameter	Example	Description
   Region	CN-Hong Kong	For low network latency and quick resource access, select the region nearest to your target users. After a FlexusL instance is created, the region cannot be changed. Exercise caution when selecting a region.
   Application Image	PrestaShop	Select the PrestaShop application image.
   Instance Specifications	2 vCPUs | 2 GiB | System disk 60 GiB	Select instance specifications as needed.
   Instance Name	PrestaShop-Example	Customize an instance name that is easy to identify, for example, PrestaShop-Example.
   (Optional) Associated Services	Data Disk: 10 GiB Host Security Cloud backup vault: 70 GiB	You can bundle any of EVS, HSS (basic edition), and CBR to your FlexusL instances as needed and set specifications as needed.
   Required Duration	1 month	The minimum duration of a purchase is one month and the maximum duration is three years. Auto-renew is enabled by default, which means the purchased FlexusL instances will be automatically renewed before they expire. If you do not enable auto-renew during the purchase process, you can still enable it later after the instances are created. For more information about auto-renewal rules, see Auto-Renewal Rules.
   Quantity	1	Set the number of FlexusL instances to be purchased.

3. Click Buy Now and complete the payment as prompted.
4. Go back to the FlexusL console and view the purchased FlexusL instance.

Step 2: Configure Security Groups

Add inbound security group rules to ensure that the application preinstalled in the image can be accessed.

1. Log in to the FlexusL console and click a resource card to go to the instance details page.
2. In the navigation pane on the left, choose Cloud Servers. Locate the server and click its name.

   

3. On the Security Groups tab, click Add Rule. In the displayed dialog box, add rules displayed in the following figure and click OK.

   The following figure only displays common rules. You can add more rules as needed.

   Table 1 Security group rules

   Priority	Action	Type	Protocol & Port	Source	Description
   1	Allow	IPv4	TCP: 80	0.0.0.0/0	Specifies the internal forwarding port of application images
   1	Allow	IPv4	TCP: 3306	0.0.0.0/0	Allows access to MySQL databases.
   1	Allow	IPv4	TCP: 9000	0.0.0.0/0	Allows external access to the application O&M page.
   1	Allow	IPv4	TCP: 9001	0.0.0.0/0	Allows external access to the application dashboard.

Step 3: Reset a Password

A FlexusL instance does not have an initial password. After creating a FlexusL instance, set a password for the FlexusL instance. The password of the FlexusL instance is also used for logging in to the O&M page of the application.

1. In the Image area on the Overview page of the FlexusL console, click Access to go to the application dashboard and check whether the application has been up and running. If yes, go to the next step.
   

   Wait for several minutes until the image with the pre-installed application is up and running. Then, you can perform operations such as restarting or stopping the instance, or resetting the password. Otherwise, the initial password may become invalid and you cannot log in to the application dashboard.

   Figure 1 Entry to the application dashboard
   
   

   When you click Access to go to the dashboard for the first time, PrestaShop generates a random character string following the dashboard address for encryption. Keep the encrypted dashboard address in mind. You can only use the encrypted address to log in to the dashboard and cannot access the dashboard from the console..

   For example, when you access the management console http://1.1.1.1:9001/admin for the first time, the address automatically changes to http://1.1.1.1:9001/admin923reep1k/index……, where the character string 923reep1k is added after admin. Keep the address http://1.1.1.1:9001/admin923reep1k in mind. (You do not need to record the part following admin923reep1k/)

   You can also reinstall the FlexusL instance to obtain the new dashboard address, but the original data will be lost. Therefore, keep the encrypted address in mind.

   After the application is started, the initialization wizard page of the dashboard is displayed, as shown in Figure 2.

   Figure 2 Initialization wizard page of the Prestashop dashboard
   
   

   If the dashboard is not properly displayed, check the following causes:

   • The port for accessing the dashboard is not allowed. Check whether the port is allowed based on Step 2: Configure Security Groups.
   • The dashboard is being started. Try again later.
2. Locate the resource card and choose > Reset Password to reset the password.

   For details, see Resetting the Password for a FlexusL Instance.

   Figure 3 Resetting a password
   
   

   The password for logging in to the FlexusL instance is also the password for logging in to the O&M page of the application.

Step 4: Initialize Prestashop

Application images use code-based Ubuntu. They provide graphical user interfaces to make your operations easier. You need to initialize the application dashboard upon the first login. Then you can directly log in to the dashboard from the FlexusL console afterwards.

1. In the address bar of a local browser, enter http://<Server-EIP>:9000 to log in to the application O&M page.

   The initial username and password for logging in to the application dashboard are stored on the O&M page of the application. You need to log in to the O&M page first to obtain the username and password. The username for logging in to the O&M page is root, and the login password is the password reset in 2.

   

   For details about the FlexusL instances, O&M page, and dashboard, see What Is the Relationship Among FlexusL Instances, the Dashboard, and the O&M Page?

2. On the My Apps page, click the application icon, choose Access, and click Initial Account to view the username and password for logging in to the application management page.

   The initial password is a randomly generated strong password. After the application is initialized, change the password on the dashboard for easy management. If the password is changed, the initial password will be invalid. Remember the new password.

   

3. On the Overview page, click Access in the Dashboard field in the Image area.

   

   

   If the dashboard is not properly displayed, check the following causes:

   • The port for accessing the dashboard is not allowed. Check whether the port is allowed based on Step 2: Configure Security Groups.
   • The dashboard is being started. Try again later.
4. Enter the password obtained in 2.
   Figure 4 Initialization wizard page of the Prestashop dashboard
   
   

   If a message is displayed indicating that the username or password you entered is invalid when you attempt to log in to the application dashboard, refer to Why Can't I Access the Dashboard of the Application Pre-installed in the Application Image After Entering the Initial Username and Password?

5. Click LOG IN to log in to PrestaShop.

   

After the Prestashop application is initialized, you can deploy your applications on the dashboard.

Step 5: Deploy Prestashop

This section describes some basic operations of PrestaShop. For more information, see PrestaShop Documentation.