Bitnami PrestaShop for Huawei

Enterprise Cloud

Description

PrestaShop is a popular open source ecommerce solution. Professional tools

are easily accessible to increase online sales including instant guest

checkout, abandoned cart reminders and automated Email marketing.

First steps with the Bitnami PrestaShop

Stack

Welcome to your new Bitnami application running on Huawei Enterprise

Cloud! Here are a few questions (and answers!) you might need when first

starting with your application.

What is the administrator username set for me to log in to the

application for the first time?

Username: user@example.com

What is the administrator password?

To obtain the administrator password, click the "Remote Login" menu option

next to the server name in the Huawei Cloud Server Console. This will launch

a new browser window with an encrypted login session. The application

password will be displayed on the login welcome screen.

What SSH username should I use for secure shell access to

my application?

SSH username: root

How to connect to the MySQL database?

You can connect to the MySQL database from the same computer where it is

installed with the mysql client tool.

mysql -u root -p

You will be prompted to enter the root user password. This is the same as the

application password.

Find out how to obtain application credentials.

How to debug errors in your database?

The main log file is created at /opt/bitnami/mysql/data/mysqld.log on the

MySQL database server host.

How to start or stop the services?

Each Bitnami stack includes a control script that lets you easily stop, start and

restart services. The script is located at /opt/bitnami/ctlscript.sh. Call it without

any service name arguments to start all services:

sudo /opt/bitnami/ctlscript.sh start

Or use it to restart a single service, such as Apache only, by passing the

service name as argument:

sudo /opt/bitnami/ctlscript.sh restart apache

Use this script to stop all services:

sudo /opt/bitnami/ctlscript.sh stop

Restart the services by running the script without any arguments:

sudo /opt/bitnami/ctlscript.sh restart

Obtain a list of available services and operations by running the script without

any arguments:

sudo /opt/bitnami/ctlscript.sh

Updating the IP address or hostname

PrestaShop requires updating the IP address/domain name if the machine IP

address/domain name changes. The bnconfig tool also has an option which

updates the IP address, called –machine_hostname (use –help to check if

that option is available for your application). Note that this tool changes the

URL to http://NEW_DOMAIN/prestashop.

sudo /opt/bitnami/apps/prestashop/bnconfig --machine_hostname NEW_DOMAIN

If you have configured your machine to use a static domain name or IP

address, you should rename or remove the

/opt/bitnami/apps/prestashop/bnconfig file.

sudo mv /opt/bitnami/apps/prestashop/bnconfig /opt/bitnami/apps/prestash

op/bnconfig.disabled

NOTE: Be sure that your domain is propagated. Otherwise, this will not work.

You can verify the new DNS record by using the Global DNS Propagation

Checker and entering your domain name into the search field.

You can also change your hostname by modifying it in your hosts file. Enter

the new hostname using your preferred editor.

sudo nano /etc/hosts

Add a new line with the IP address and the new hostname. Here's an

example. Remember to replace the IP-ADDRESS and DOMAIN

placeholders with the correct IP address and domain name.

IP-ADDRESS DOMAIN

How to create a full backup of PrestaShop?

Backup

The Bitnami PrestaShop Stack is self-contained and the simplest option for

performing a backup is to copy or compress the Bitnami stack installation

directory. To do so in a safe manner, you will need to stop all servers, so this

method may not be appropriate if you have people accessing the application

continuously.

Follow these steps:

Change to the directory in which you wish to save your backup:

cd /your/directory

Stop all servers:

sudo /opt/bitnami/ctlscript.sh stop

Create a compressed file with the stack contents:

sudo tar -pczvf application-backup.tar.gz /opt/bitnami

Restart all servers:

sudo /opt/bitnami/ctlscript.sh start

You should now download or transfer the application-backup.tar.gz file to a

safe location.

Restore

Follow these steps:

Change to the directory containing your backup:

cd /your/directory

Stop all servers:

sudo /opt/bitnami/ctlscript.sh stop

Move the current stack to a different location:

sudo mv /opt/bitnami /tmp/bitnami-backup

Uncompress the backup file to the original directoryv

sudo tar -pxzvf application-backup.tar.gz -C /

Start all servers:

sudo /opt/bitnami/ctlscript.sh start

If you want to create only a database backup, refer to these instructions for

MySQL and PostgreSQL.

How to configure outbound email settings?

Go to the "Administration" section and click the "Advanced Parameters -> E-

mail" section. Configure the SMTP settings to allow the application to send

emails.

Below is a sample configuration using a Gmail account. Replace USERNAME

and PASSWORD with your Gmail account username and password

respectively.

Mail domain name: SERVER-IP

SMTP server: smtp.gmail.com

SMTP user: USERNAME@gmail.com

SMTP password: PASSWORD

Encryption: SSL

Port: 465

It is possible to test the configuration on the same page.

To configure the application to use other third-party SMTP services for

outgoing email, such as SendGrid or Mandrill, refer to the FAQ.

Troubleshooting Gmail SMTP issues

If you are using Gmail as the outbound email server and you are not able to

send email correctly, Google may be blocking sign-in attempts from your apps

or devices. Depending on whether or not you use Google Apps, the steps to

correct this will differ.

For Google Apps users

If you are a Google Apps user, you will need your administrator to allow users

to change the policy for less secure apps. If you are a Google Apps

administrator, follow these steps:

Browse to the Google Apps administration panel.

Click on "Security" and then "Basic settings".

Look for the section "Less secure apps" and then click on "Go to

settings for less secure apps".

Select "Allow users to manage their access to less secure apps".

For other Google users

If you do not use Google Apps, follow the steps in the following sections,

depending on whether 2-step verification has been enabled on the account or

not.

If 2-step verification has not been enabled on the account, follow these steps:

Browse to the "Less secure apps" page and log in using the account

you are having problems with. This option is typically required by many

popular email clients, such as Outlook and Thunderbird, and should not

be considered unsafe.

Select the "Turn on" option.

If 2-step verification has been enabled on the account, you have to generate

an app password. Follow these steps:

Browse to the "App passwords" page.

Click "Select app" and choose the app you're using.

Click "Select device" and choose the device you're using.

Click the "Generate" button.

Enter the app password on your device.

Click the "Done" button.

Here are other options you may try:

Browse to the web version of Gmail and sign in to your account.

Once you're signed in, try to enable access for the application again.

Browse to the "Unlock Captcha" function page and sign in with your

Gmail username and password.

Disable IMAP from the Gmail web server interface and enable it again.

How to upload files to the server with SFTP?

Although you can use any SFTP/SCP client to transfer files to your server, the

link below explains how to configure FileZilla (Windows, Linux and Mac OS

X), WinSCP (Windows) and Cyberduck (Mac OS X). It is required to use your

server's private SSH key to configure the SFTP client properly. Choose your

preferred application and follow the steps in the link below to connect to the

server through SFTP.

How to upload files to the server

How to enable HTTPS support with SSL

certificates?

NOTE: The steps below assume that you are using a custom domain name

and that you have already configured the custom domain name to point to

your cloud server.

Bitnami images come with SSL support already pre-configured and with a

dummy certificate in place. Although this dummy certificate is fine for testing

and development purposes, you will usually want to use a valid SSL certificate

for production use. You can either generate this on your own (explained here)

or you can purchase one from a commercial certificate authority.

Once you obtain the certificate and certificate key files, you will need to

update your server to use them. Follow these steps to activate SSL support:

Use the table below to identify the correct locations for your certificate

and configuration files.

Variable Value

Current

application URL https://[custom-domain]/

Example: https://my-domain.com/ or https://my-

domain.com/appname

Apache

configuration file /opt/bitnami/apache2/conf/bitnami/bitnami.conf

Certificate file /opt/bitnami/apache2/conf/server.crt

Certificate key file /opt/bitnami/apache2/conf/server.key

CA certificate

bundle file (if

present)

/opt/bitnami/apache2/conf/server-ca.crt

Copy your SSL certificate and certificate key file to the specified

locations.

NOTE: If you use different names for your certificate and key files, you should

reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the

corresponding Apache configuration file to reflect the correct file names.

If your certificate authority has also provided you with a PEM-encoded

Certificate Authority (CA) bundle, you must copy it to the correct

location in the previous table. Then, modify the Apache configuration

file to include the following line below the SSLCertificateKeyFile

directive. Choose the correct directive based on your scenario and

Apache version:

Variable Value

Apache

configuration file /opt/bitnami/apache2/conf/bitnami/bitnami.conf

Directive to include

(Apache v2.4.8+)

SSLCACertificateFile

"/opt/bitnami/apache2/conf/server-ca.crt"

Directive to include

(Apache < v2.4.8)

SSLCertificateChainFile

"/opt/bitnami/apache2/conf/server-ca.crt"

NOTE: If you use a different name for your CA certificate bundle, you should

reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in

the corresponding Apache configuration file to reflect the correct file name.

Once you have copied all the server certificate files, you may make

them readable by the root user only with the following commands:

sudo chown root:root /opt/bitnami/apache2/conf/server*

sudo chmod 600 /opt/bitnami/apache2/conf/server*

Open port 443 in the server firewall. Refer to the FAQ for more

information.

Restart the Apache server.

You should now be able to access your application using an HTTPS URL.

How to create an SSL certificate?

You can create your own SSL certificate with the OpenSSL binary. A

certificate request can then be sent to a certificate authority (CA) to get it

signed into a certificate, or if you have your own certificate authority, you may

sign it yourself, or you can use a self-signed certificate (because you just want

a test certificate or because you are setting up your own CA).

Create your private key (if you haven't created it already):

sudo openssl genrsa -out /opt/bitnami/apache2/conf/server.key 2048

Create a certificate:

sudo openssl req -new -key /opt/bitnami/apache2/conf/server.key -o

ut /opt/bitnami/apache2/conf/cert.csr

IMPORTANT: Enter the server domain name when the above

command asks for the "Common Name".

Send cert.csr to the certificate authority. When the certificate authority

completes their checks (and probably received payment from you),

they will hand over your new certificate to you.

Until the certificate is received, create a temporary self-signed

certificate:

sudo openssl x509 -in /opt/bitnami/apache2/conf/cert.csr -out /opt

/bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apach

e2/conf/server.key -days 365

Back up your private key in a safe location after generating a

password-protected version as follows:

sudo openssl rsa -des3 -in /opt/bitnami/apache2/conf/server.key -o

ut privkey.pem

Note that if you use this encrypted key in the Apache configuration file,

it will be necessary to enter the password manually every time Apache

starts. Regenerate the key without password protection from this file as

follows:

sudo openssl rsa -in privkey.pem -out /opt/bitnami/apache2/conf/se

rver.key

Find more information about certificates at http://www.openssl.org.

How to force HTTPS redirection?

Add the following to the top of the /opt/bitnami/apps/prestashop/conf/httpd-

prefix.conf file:

RewriteEngine On

RewriteCond %{HTTPS} !=on

RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]

After modifying the Apache configuration files, restart Apache to apply the

changes.

How to debug Apache errors?

Once Apache starts, it will create two log files at

/opt/bitnami/apache2/logs/access_log and /opt/bitnami/apache2/logs/error_log

respectively.

The access_log file is used to track client requests. When a client

requests a document from the server, Apache records several

parameters associated with the request in this file, such as: the IP

address of the client, the document requested, the HTTP status code,

and the current time.

The error_log file is used to record important events. This file includes

error messages, startup messages, and any other significant events in

the life cycle of the server. This is the first place to look when you run

into a problem when using Apache.

If no error is found, you will see a message similar to:

Syntax OK

How to modify PHP settings?

The PHP configuration file allows you to configure the modules enabled, the

email settings or the size of the upload files. It is located at

/opt/bitnami/php/etc/php.ini.

After modifying the PHP configuration file, restart both Apache and PHP-FPM

for the changes to take effect:

sudo /opt/bitnami/ctlscript.sh restart apache

sudo /opt/bitnami/ctlscript.sh restart php-fpm

For example, to modify the default upload limit for PHP, update the PHP

configuration file following these instructions.

How to modify the allowed limit for uploaded

files?

Modify the following options in the /opt/bitnami/php/etc/php.ini file to increase

the allowed size for uploads:

; Maximum size of POST data that PHP will accept.

post_max_size = 16M

; Maximum allowed size for uploaded files.

upload_max_filesize = 16M

Restart PHP-FPM and Apache for the changes to take effect.

sudo /opt/bitnami/ctlscript.sh restart apache

sudo /opt/bitnami/ctlscript.sh restart php-fpm

How to access phpMyAdmin?

For security reasons, phpMyAdmin is accessible only when using 127.0.0.1

as the hostname. To access it from a remote system, you must create an

SSH tunnel that routes requests to the Apache Web server from 127.0.0.1.

This implies that you must be able to connect to your server over SSH in

order to access these applications remotely.

IMPORTANT: Before following the steps below, ensure that your Apache and

MySQL servers are running.

NOTE: The steps below suggest using port 8888 for the SSH tunnel. If this

port is already in use by another application on your local machine, replace it

with any other port number greater than 1024 and modify the steps below

accordingly. Similarly, if you have enabled Varnish, your stack's Apache Web

server might be running on port 81. In this case, modify the steps below to

use port 81 instead of port 80 for the tunnel endpoint.

Windows

To access the application using your Web browser, create an SSH tunnel, as

described below.

Download PuTTY and make sure you can log in to the server console

with it following the instructions in the FAQ. Once you have confirmed

you are able to log in successfully, log back out.

Reconnect to the server using PuTTY, this time adapting the steps to

include an additional SSH tunnel. When configuring the new SSH

session in PuTTY, additionally navigate to the "Connection -> SSH ->

Tunnels" section and create a secure tunnel by forwarding port 80 on

the server to port 8888 on the local host (127.0.0.1 or localhost).

Click the "Add" button to add the secure tunnel configuration to the

session. Here is an example:

Go back to the "Session" section and save your changes by clicking

the "Save" button.

Click the "Open" button to open an SSH session to the server. The

SSH session will now include a secure SSH tunnel between the two

specified ports.

While the tunnel is active, you should be able to access the phpMyAdmin

console through the secure SSH tunnel you created, by browsing to

http://127.0.0.1:8888/phpmyadmin.

To log in, use username root for MySQL and the application password from

the detail page for your cloud server.

If you are unable to access phpMyAdmin, verify that the SSH tunnel was

created by checking the PuTTY event log (accessible via the "Event Log"

menu):

Linux and Mac OS X

To access the application using your Web browser, create an SSH tunnel, as

described below.

Open a new terminal window on your local system (for example, using

"Finder -> Applications -> Utilities -> Terminal" in Mac OS X or the

Dash in Ubuntu).

Make sure you can log in to the server console following the

instructions in the FAQ. Once you have confirmed you are able to log in

successfully, log back out.

Run the following command to configure the SSH tunnel. Remember to

replace SERVER-IP with the public IP address or hostname of your

server. Enter your SSH password when prompted.

ssh -N -L 8888:127.0.0.1:80 bitnami@SERVER-IP

If you are using a private key to connect to the server, use the following

command instead, remembering to replace KEYFILE with the path to

your private key and SERVER-IP with the public IP address or

hostname of your server:

ssh -N -L 8888:127.0.0.1:80 -i KEYFILE bitnami@SERVER-IP

NOTE: If successful, the above commands will create an SSH tunnel

but will not display any output on the server console.

While the tunnel is active, you should be able to access the phpMyAdmin

console through the secure SSH tunnel you created, by browsing to

http://127.0.0.1:8888/phpmyadmin.

To log in, use username root for MySQL and the application password from

the detail page for your cloud server.

How to configure PrestaShop with

memcached?

Follow these steps:

Log in to the server console.

Enable and start the memcached service. Memcached services will run

on port 11211 by default so shouldn't affect any other components.

Execute the following commands:

sudo mv /opt/bitnami/memcached/scripts/ctl.sh.disabled /opt/bitna

mi/memcached/scripts/ctl.sh

sudo /opt/bitnami/ctlscript.sh start memcached

Enable the PHP memcache extension by editing the

/opt/bitnami/php/etc/php.ini file and removing the semicolon (;) at the

beginning of the following line:

extension=memcache.so

Restart PHP-FPM and Apache services:

sudo /opt/bitnami/ctlscript.sh restart php-fpm

sudo /opt/bitnami/ctlscript.sh restart apache

Set the correct permissions on .htaccess files:

sudo chmod 660 /opt/bitnami/apps/prestashop/htdocs/.htaccess

Log in to the PrestaShop Web administration panel and navigate to the

"Advanced Parameters -> Performance page".

Find the "Caching" section of the page and set the "Use cache" option

to "Yes". Check the "Memcached via PHP::Memcache" option.

Save the changes by clicking the "Save" button.

Within the "Caching" section again, click the "Add Server" button. In the

resulting form, set the "IP Address" to "127.0.0.1" and the "Port" to

"11211".

Click the "Test Server" button to check that the connection details are

correct.

Click the "Add Server" button to save the configuration.

How to enable SSL?

NOTE: Ensure that the Apache server is already configured to enable SSL

connections.

To enable SSL on all pages, follow these steps:

Browse to the administration panel and log in.

Click "Preferences" in the left navigation panel.

Set the option "Enable SSL on all pages" to "Yes".

Click the "Save" button.

How to optimize PrestaShop with Varnish?

NOTE: The steps below assume that PrestaShop is configured to run at the

root of the domain.

Follow the steps below to configure PrestaStop with Varnish:

Connect to the server via SSH.

Start the Varnish service on port 81 by executing the following

commands:

sudo mv /opt/bitnami/varnish/scripts/ctl.sh.disabled /opt/bitnami

/varnish/scripts/ctl.sh

sudo /opt/bitnami/ctlscript.sh start varnish

Back up the original Varnish configuration file:

sudo cp /opt/bitnami/varnish/etc/varnish/default.vcl /opt/bitnami

/varnish/etc/varnish/default.vcl.backup

Add the PrestaShop-specific Varnish configuration by downloading the

corresponding file and copying it to the correct location:

sudo cp prestashop.v4 /opt/bitnami/varnish/etc/varnish/default.vc

l

sudo sed -i 's/port\s*=\s*"[^"]*"/port = "80"/g' /opt/bitnami/varn

ish/etc/varnish/default.vcl

Varnish and PrestaShop are now configured.

IMPORTANT: Varnish is connected to Apache locally so other applications

like phpMyAdmin or phpPgAdmin could become public. Find out how to

block these applications.

Next, proceed to test and activate the Varnish service as described below:

Restart the Varnish service:

sudo /opt/bitnami/ctlscript.sh restart varnish

Open port 81 in the server firewall. Refer to the FAQ for instructions.

Check if the website is being served properly by Varnish on port 81, by

browsing to http://SERVER-IP:81 or by using an online tool like

http://www.isvarnishworking.com.

If Varnish is working correctly, switch the Apache and Varnish ports

and activate Varnish on port 80:

cd /opt/bitnami

sudo sed -i 's/^\s*Listen .*$/Listen 81/g' apache2/conf/httpd.conf

sudo sed -i 's/\:80/\:81/g' apache2/conf/bitnami/bitnami.conf

sudo sed -i 's/at port.*"/at port 81"/g' apache2/scripts/ctl.sh

sudo sed -i 's/\:80/\:81/g' apps/*/conf/httpd-vhosts.conf

sudo sed -i 's/=80/=81/g' properties.ini

sudo sed -i 's/port\s*=\s*"[^"]*"/port = "81"/g' varnish/etc/varni

sh/default.vcl

sudo sed -i 's/VARNISH_PORT=.*$/VARNISH_PORT=80/g' varnish/scripts

/ctl.sh

Restart the services:

sudo /opt/bitnami/ctlscript.sh restart

Remove the firewall rule added for port 81.

IMPORTANT: Varnish does not cache content if the Apache PageSpeed

module is enabled. Find out how to disable this module.

IMPORTANT: If using bnconfig, set the server port to 80 or 8080 before

running it, then change it back to 81 or 8081 after, as shown below:

sudo sed -i 's/=81/=80/g' properties.ini

sudo apps/APPNAME/bnconfig --option parameter

sudo sed -i 's/=80/=81/g' properties.ini

sudo /opt/bitnami/ctlscript.sh restart

How to enable PrestaShop Multistore

support?

Follow these steps:

Login to your administration console, at http://DOMAIN/administration.

Navigate to the "Preferences -> General" menu, enable the Multistore

support and save your changes.

Navigate to the "Advanced Parameters -> Multistore" menu. You can

share the same Store Group or add a new one. This example shares

the Default Store Group. Go to your default shop (called "PrestaShop"

in this example), and click the "Add new shop" button

Enter the shop name, choose the associated categories and the data

you want to import from another shop (if needed). You will not be able

to revert these settings. Click "Save" once done.

Change the URL by clicking the "Click here to set a URL for this shop".

Enter the "Domain" and "SSL Domain" for the new shop. Also, choose

the "Physical URL" (by default /prestashop/ but change it to / if you

moved PrestaShop to the root URL). Save the changes.

Edit the /opt/bitnami/apps/prestashop/conf/htaccess.conf file and add

the following lines (replacing the example domain example.com with

your shop domain) inside the IfModule mod_rewrite.c section.

<IfModule mod_rewrite.c>

...

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule . - [E=REWRITEBASE:/prestashop/]

RewriteRule ^api/?(.*)$ %{ENV:REWRITEBASE}webservice/dispatcher.

php?url=$1 [QSA,L]

# Images

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{EN

V:REWRITEBASE}img/p/$1/$1$2$3.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg

$ %{ENV:REWRITEBASE}img/p/$1/$2/$1$2$3$4.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?

/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$1$2$3$4$5.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0

-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$1$2$3$4$5$6.

jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]

*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$1

$2$3$4$5$6$7.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA

-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4

/$5/$6/$1$2$3$4$5$6$7$8.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\

-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/

$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])

([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}i

mg/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^c/([0-9]+)(\-[\.*_a-zA-Z0-9-]*)(-[0-9]+)?/.+\.jpg

$ %{ENV:REWRITEBASE}img/c/$1$2$3.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^c/([a-zA-Z_-]+)(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBAS

E}img/c/$1$2.jpg [L]

# AlphaImageLoader for IE and fancybox

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^images_ie/?([^/]+)\.(jpe?g|png|gif)$ js/jquery/plug

ins/fancybox/images/$1.$2 [L]

# Dispatcher

RewriteCond %{REQUEST_FILENAME} -s [OR]

RewriteCond %{REQUEST_FILENAME} -l [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^.*$ - [NC,L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^.*$ %{ENV:REWRITEBASE}index.php [NC,L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule . - [E=REWRITEBASE:/prestashop/]

RewriteRule ^api/?(.*)$ %{ENV:REWRITEBASE}webservice/dispatcher.

php?url=$1 [QSA,L]

# Images

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{EN

V:REWRITEBASE}img/p/$1/$1$2$3.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com$

RewriteRule ^([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg

$ %{ENV:REWRITEBASE}img/p/$1/$2/$1$2$3$4.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?

/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$1$2$3$4$5.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0

-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$1$2$3$4$5$6.

jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]

*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$1

$2$3$4$5$6$7.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA

-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4

/$5/$6/$1$2$3$4$5$6$7$8.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\

-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}img/p/$1/

$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])

([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBASE}i

mg/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^c/([0-9]+)(\-[\.*_a-zA-Z0-9-]*)(-[0-9]+)?/.+\.jpg

$ %{ENV:REWRITEBASE}img/c/$1$2$3.jpg [L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^c/([a-zA-Z_-]+)(-[0-9]+)?/.+\.jpg$ %{ENV:REWRITEBAS

E}img/c/$1$2.jpg [L]

# AlphaImageLoader for IE and fancybox

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^images_ie/?([^/]+)\.(jpe?g|png|gif)$ js/jquery/plug

ins/fancybox/images/$1.$2 [L]

# Dispatcher

RewriteCond %{REQUEST_FILENAME} -s [OR]

RewriteCond %{REQUEST_FILENAME} -l [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^.*$ - [NC,L]

RewriteCond %{HTTP_HOST} ^example.com:443$

RewriteRule ^.*$ %{ENV:REWRITEBASE}index.php [NC,L]

...

</IfModule>

Restart your Apache server

sudo /opt/bitnami/ctlscript.sh restart apache

You should now be able to access your new shop.

What are the default optimizations in the

Bitnami Prestashop Stack?

The Bitnami Prestashop Stack includes sets a number of variables for

performance optimization by default. You can modify these to suit your

requirements through the PrestaShop administration panel. Here's a quick list:

Page templates are compiled only once and then cached. Modify this

via the "Administration -> Advanced Parameters -> Performance"

page.

CSS and JavaScript files are automatically cached. HTML and

JavaScript files are automatically compressed for quicker transmission.

Modify this via the "Administration -> Advanced Parameters ->

Performance" page.

Friendly URLs are enabled by default. Modify this via the

"Administration -> Preferences -> SEO & URLs" page.

How to upgrade PrestaShop?

It is strongly recommended to create a backup before starting the update

process. If you have important data, create and try to restore a backup to

ensure that everything works properly.

You can upgrade PrestaShop using the "1-Click Upgrade" module. To do so,

follow these steps:

Modify the owner of the htdocs folder.

sudo chown -R daemon:daemon /opt/bitnami/apps/prestashop/htdocs

If your PrestaShop version is older than 1.6, remove the .htaccess file

in the htdocs folder

cd /opt/bitnami/apps/prestashop/htdocs

sudo find -name .htaccess -delete

Access your Prestashop administration console using your browser.

Navigate to the "Modules -> Modules" menu and install the "1-Click

Upgrade" module.

Once installed, click the "Update It" button for the "1-Click Upgrade"

module. This brings up the checklist for performing the upgrade.

You should see a single red X on the list. This is because the site is not

yet in Maintenance Mode. Click the button to set it to Maintenance

Mode.

Click the "Upgrade PrestaShop Now!" link and wait until the upgrade

process is finished.

Access the administration console again, navigate to the "Preferences

-> Maintenance" menu and "Enable" your shop.

Check that your site is working correctly.

Modify the owner of the htdocs folder as below.

sudo chown -R bitnami:daemon /opt/bitnami/apps/prestashop/htdocs