====== Docker Options ======

Docker makes it easy to jump in and have a perfect environment for working on Wizard's Toolkit. Plus, Docker facilitates scaling through Kubernetes and other methods. Wizard's Toolkit provides what we think is an ideal environment, but since this is low-code, you are welcome to change any aspects you want.

===== WTK Mysql Docker =====

The default Docker environment for Wizard's Toolkit as defined in **docker-compose.yml** contains:

  * Nginx - nginx:1.22.0-alpine (see `/nginx.conf` for details)
  * PHP - php:8.1-fpm (see `PHP.Dockerfile` for details)
    * PHP environment variables are set in `/phpMySQL.env`
  * **MySQL** - mysql:8.3
  * phpMyAdmin - You may want to remove this before deploying to production.

To build, simply run in Terminal:

<code Terminal>
./WTK.sh
</code>

===== WTK PostgreSQL Docker =====

There is an alternative docker-composePG.yml file which contains the PostgreSQL version of Wizard's Toolkit. All the web pages are the same, but the database is PostgreSQL.

To run, rename the  **docker-compose.yml** to **docker-composeMySQL.yml** then rename the **docker-composePG.yml** to **docker-compose.yml**. After that, build your Docker environment by simply running in Terminal:

<code>
./WTK.sh
</code>

The docker-composePG.yml contains:

  * Nginx - nginx:1.22.0-alpine (see `/nginx.conf` for details)
  * PHP - php:8.1-fpm (see **PHP.DockerfilePG** for details)
    * PHP environment variables are set in **/phpPG.env**
  * **PostgreSQL** - bitnami/postgresql:latest

===== WTK MySQL and Python Code =====

If you need your web server to also process Python, a Docker container has been provided which contains all the images in the core MySQL container, plus an image with Python and Gunicorn. The port is not exposed to the public and is only accessible by the PHP pages via internal networking.

The **docker-composePython.yml** contains the following:

  * Nginx - nginx:1.22.0-alpine (see /nginx.conf for details)
  * PHP - php:8.1-fpm (see PHP.Dockerfile for details)
    * PHP environment variables are set in /phpMySQL.env
  * MySQL - mysql:8.3
  * phpMyAdmin - you may want to remove this before publishing to production
  * Python - python:3.11.4-alpine3.18 (see Python.Dockerfile for details which pulls files from /python)

To use this, simply rename the **docker-composePython.yml** to **docker-compose.yml**. After that, build your Docker environment as normal or in Terminal simply run:

<code>
./STOP_CONTAINERS.sh
./WTK.sh
</code>

Demo pages have been provided as a prototype for connectivity between your WTK PHP pages and your Python file(s).

After creating an account to log in, go to:

http://127.0.0.1/demo/python.php

Log in, then click the **Python Test** links. These pass a parameter to **/demo/getPython.php** and display the results on the web page. The getPython.php page only contains the following:

<code php>
<?PHP
$pgSecurityLevel = 1;
define('_RootPATH', '../');
require('../wtk/wtkLogin.php');

$pgStep = wtkGetPost('step');
// modify calling method to pass as many parameters as you want, then pass those to your Python page

// wtk_python is your Docker Python image name
$pgPythonURL = "http://wtk_python:5000/?step=$pgStep";
$pgResponse  = file_get_contents($pgPythonURL);

echo $pgResponse;
exit;
?>
</code>

==== Python Code Location ====

The Python code is all in the **/python/app.py** file. During Docker build, it is copied to an `/app` folder within the image, which is not accessible to the public but is accessible to the other images in your Docker `wizardstoolkit` container.

The associated files for the Python build are in the `/python` folder.

Currently, the `app.py` simply sends various responses depending on what parameters are sent. This is just a working prototype that you can build from.