If You want to build a reverse proxy website with PrestaShop at short time;
  Â
  Â
Plus, manage docker containers with Portainer.
arm64/aarch64, x86-64
apk, dnf, yum, apt/apt-get, zypper
  Â
Note: Fedora 37, 39 and alpine linux x86-64 compatible, could not try sles IBM Z s390x, rhel IBM Z s390x and raspberrypi.
- PrestaShop - php-fpm
- webserver (apache2/httpd)
- proxy (nginx)
- certbot (letsencrypt)
- phpMyAdmin
- databaseMariadb databaseMysql
- backup
Create rules to open ports to the internet, or to a specific IPv4 address or range.
- http: 80
- https: 443
- portainer: 9001
- phpmyadmin: 9090
If you are using a system with less than 2 GB of RAM, we recommend you create a swap file; otherwise, your install might fail.
- Auto Configuration and Installation
- Requirements
- Manual Configuration and Installation
- Portainer Installation
- Usage
download with
git clone https://github.com/damalis/full-stack-proxy-nginx-prestashop-for-everyone-with-docker-compose.git
Open a terminal and cd to the folder in which docker-compose.yml is saved and run:
cd full-stack-proxy-nginx-prestashop-for-everyone-with-docker-compose
chmod +x install.sh
./install.sh
Make sure you have the latest versions of Docker and Docker Compose installed on your machine.
Clone this repository or copy the files from this repository into a new folder.
Make sure to add your user to the docker group.
download with
git clone https://github.com/damalis/full-stack-proxy-nginx-prestashop-for-everyone-with-docker-compose.git
Open a terminal and cd to the folder in which docker-compose.yml is saved and run:
cd full-stack-proxy-nginx-prestashop-for-everyone-with-docker-compose
Copy the example environment into .env
cp env.example .env
Edit the .env file to change values of LOCAL_TIMEZONE, DOMAIN_NAME, DIRECTORY_PATH, LETSENCRYPT_EMAIL, DB_USER, DB_PASSWORD, DB_NAME, DB_TABLE_PREFIX, MYSQL_ROOT_PASSWORD, DATABASE_IMAGE_NAME, DATABASE_CONT_NAME, DATABASE_PACKAGE_MANAGER, DATABASE_ADMIN_COMMANDLINE, PMA_CONTROLUSER, PMA_CONTROLPASS, PMA_HTPASSWD_USERNAME and PMA_HTPASSWD_PASSWORD.
LOCAL_TIMEZONE=to see local timezones
DIRECTORY_PATH=pwd at command line
DATABASE_IMAGE_NAME=mariadb or mysql
DATABASE_CONT_NAME=mariadb, mysql or custom name
DATABASE_PACKAGE_MANAGER=apt-get update && apt-get install -y gettext-base for mariadb, microdnf install -y gettext for mysql
DATABASE_ADMIN_COMMANDLINE=mariadb-admin for mariadb, mysqladmin for mysql
and
cp ./phpmyadmin/apache2/sites-available/default-ssl.sample.conf ./phpmyadmin/apache2/sites-available/default-ssl.conf
change example.com to your domain name in ./phpmyadmin/apache2/sites-available/default-ssl.conf file.
cp ./database/phpmyadmin/sql/create_tables.sql.template.example ./database/phpmyadmin/sql/create_tables.sql.template
change pma_controluser and db_authentication_password in ./database/phpmyadmin/sql/create_tables.sql.template file.
Firstly: will create external volume
docker volume create --driver local --opt type=none --opt device=${PWD}/certbot --opt o=bind certbot-etc
docker compose up -d
then reloading for proxy ssl configuration
docker container restart proxy
The containers are now built and running. You should be able to access the PrestaShop installation with the configured IP in the browser address. https://example.com.
For convenience you may add a new entry into your hosts file.
docker compose -f portainer-docker-compose.yml -p portainer up -d
manage docker with Portainer is the definitive container management tool for Docker, Docker Swarm with it's highly intuitive GUI and API.
You can also visit https://example.com:9001 to access portainer after starting the containers.
The docker ps command only shows running containers by default. To see all containers, use the -a (or --all) flag:
docker ps -a
You can start the containers with the up command in daemon mode (by adding -d as an argument) or by using the start command:
docker compose start
docker compose stop
To stop and remove all the containers use the down command:
docker compose down
to remove portainer and the other containers:
docker rm -f $(docker ps -a -q)
Use -v if you need to remove the database volume which is used to persist the database:
docker compose down -v
to remove external certbot-etc and portainer and the other volumes:
docker volume rm $(docker volume ls -q)
Delete all images, containers, volumes, and networks that are not associated with a container (dangling):
docker system prune
To additionally remove any stopped containers and all unused images (not just dangling ones), add the -a flag to the command:
docker system prune -a
to remove portainer and the other images:
docker rmi $(docker image ls -q)
Copy all files into a new directory:
You can now use the up command:
docker compose up -d
https://docs.docker.com/engine/reference/run/
You should see the "PrestaShop demo site" page in your browser. If not, please check if your PHP installation satisfies PrestaShop's requirements.
https://example.com
INSERT INTO `{PREFIX}_image_type` (`id_image_type`, `name`, `width`, `height`, `products`, `categories`, `manufacturers`, `suppliers`, `stores`)
VALUES
(10, 'large_banner', 960, 400, 0, 1, 0, 0, 0),
(9, 'product_listing', 220, 220, 1, 1, 1, 1, 0),
(8, 'category_default', 960, 350, 0, 1, 0, 0, 0),
(7, 'home_default', 250, 250, 1, 0, 0, 0, 0),
(6, 'large_default', 500, 500, 1, 0, 0, 0, 0),
(5, 'medium_default', 300, 300, 1, 1, 1, 1, 0),
(4, 'small_default', 125, 125, 1, 1, 1, 1, 0),
(3, 'cart_default', 80, 80, 1, 0, 0, 0, 0);
If You get that error 'Problem: Feature was deprecated in doctrine/persistence 2.x and is not supported by installed doctrine/persistence:3.x'
composer remove doctrine/persistence:3.2.0 and composer require doctrine/persistence:2.5.7 at prestashop container.
https://example.com/admin-dev, Email address: ${LETSENCRYPT_EMAIL} and Password: ${PMA_HTPASSWD_PASSWORD} in the .env file.
add or remove code in the ./php-fpm/php/conf.d/security.ini file for custom php.ini configurations
https://www.php.net/manual/en/configuration.file.php
You should make changes custom host configurations ./php-fpm/php-fpm.d/z-www.conf then must restart service, FPM uses php.ini syntax for its configuration file - php-fpm.conf, and pool configuration files.
https://www.php.net/manual/en/install.fpm.configuration.php
docker container restart prestashop
add and/or remove prestashop site folders and files with any ftp client program in ./prestashop folder.
You can also visit https://example.com to access website after starting the containers.
Proxying is typically used to distribute the load among several servers, seamlessly show content from different websites, or pass requests for processing to application servers over protocols other than HTTP.
add or remove code in the ./proxy/templates/proxy.conf.template file for custom proxy configurations
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
add or remove code in the ./webserver/extra/httpd-vhosts.conf file for custom apache2/httpd configurations
https://httpd.apache.org/docs/2.4/
Optimize your Apache httpd configuration here.
By default, PrestaShop’s database tables start with the ps_ prefix. This can be customized during installation.
Important;
For security reasons We strongly recommend to customize your database prefix instead of using the default one. Changing it will help protect your shop against any attacks (some SQL injection for example) targeting the default table names.
https://devdocs.prestashop-project.org/8/development/database/
https://mariadb.com/kb/en/configuring-mariadb-with-option-files/
https://dev.mysql.com/doc/refman/8.3/en/
You can add your own custom config.inc.php settings (such as Configuration Storage setup) by creating a file named config.user.inc.php with the various user defined settings in it, and then linking it into the container using:
./phpmyadmin/config.user.inc.php
You can also visit https://example.com:9090 to access phpMyAdmin after starting the containers.
The first authorize screen(htpasswd;username or password) and phpmyadmin login screen the username and the password is the same as supplied in the .env file.
This will back up the all files and folders in database/dump sql and html volumes, once per day, and write it to ./backups with a filename like backup-2023-01-01T10-18-00.tar.gz
BACKUP_CRON_EXPRESSION: '20 01 * * *' the UTC timezone.