Table of contents
Foreword
Optionally, you can install phpmyadmin to access specific information or for debugging purposes.
It is not recommended. Customize the files fullchain.pem, passwd and privkey.pem in the resources directory. passwd is created with htpasswd. It contains the Apache2 passwords. Launch it by issuing the following commands:
This is absolutely not recommended, especially on production servers as this might increase security risks.
Requirements
Install the phpmyadmin package on your system.
On Ubuntu/Debian:
sudo apt install phpmyadmin
On RedHat/CentOS, the installation process is once again a bit more complex:
wget https://files.phpmyadmin.net/phpMyAdmin/4.9.4/phpMyAdmin-4.9.4-all-languages.zip unzip phpMyAdmin-4.9.4-all-languages.zip sudo mv phpMyAdmin-4.9.4-all-languages /usr/share/phpmyadmin cd /usr/share/phpmyadmin sudo mv config.sample.inc.php config.inc.php
Installation
Go to the SAMDeployment/PhpMyAdmin directory and run the following command:
make images
Run
From the same directory, simply run the following command:
make run
Update of an existing Production installation
Preserve the file Configuration.conf from the previous SAMDeployment package.
Preserve APP_KEY value from the .env file in the Server Docker. If needed, update SAMDeployment/Server/templates/laravel_env. The value of APP_KEY must be preserved. If lost, you SAM backend environment will have many issues.
Stop the containers samserver_xx.yy.zz, samphpmyadmin_xx.yy.zz and samdatabase_xx.yy.zz
Make a backup of your storage structure set using the Configuration.conf variable STORAGE_BASE_DIRECTORY
Make sure you use the latest version of SAMDeployment
Bump up the version number in the Configuration.conf file
Update Configuration.conf matching the corresponding parameters from your previous one.
Fill in any new configuration parameters.
run make images
run make run
The container databaseupdate has a very short life span. It terminates as soon as the database is updated.