Deployment script and smoke test suite for ensuring the Bitnami Ghost application is working properly.

• Docker Engine 20.10.8+
• Docker Compose 1.29.2+
• Helm 3.7.1+
• Kubernetes & kubectl 1.21.3+
• Java 11+
• Maven 3.6.1+
• Google Chrome 95+

As usual, first step is cloning the repo :)

git clone https://github.com/eduriol/bitnami-ghost-smoke-tests.git
cd  bitnami-ghost-smoke-tests

To test the deployment of Bitnami Ghost using Docker Compose, you need to run the test_compose.sh script, followed by the name of the compose yaml file you want to test. This compose yaml file contains a specific configuration for the Bitnami Ghost application, so the same script can be used to test different configurations:

./test_compose.sh <docker compose file name> 

Examples:

./test_compose.sh compose-scenario1.yml
./test_compose.sh compose-scenario2.yml 

Two compose configuration files have been attached to the repository as an example. These are the differences with respect to the original docker-compose.yml file:

compose-scenario1.yml: User and Site configuration changes. The followings config parameters have been changed:

• MARIADB_ROOT_PASSWORD=vmw@r3
• MARIADB_PASSWORD=vmw@r3
• GHOST_USERNAME=vmware
• GHOST_PASSWORD=vmw@r3p455w0rd
• GHOST_EMAIL=[email protected]
• GHOST_DATABASE_PASSWORD=vmw@r3
• GHOST_BLOG_TITLE=VMware Blog
• GHOST_PORT_NUMBER=5454
• GHOST_EXTERNAL_HTTP_PORT_NUMBER=8080

compose-scenario2.yml: Database connection configuration changes. The followings config parameters have been changed:

• MARIADB_USER=vmw_ghost
• MARIADB_DATABASE=vmware_ghost
• MARIADB_PASSWORD=dbpassword
• MARIADB_ROOT_PASSWORD=dbpassword
• GHOST_DATABASE_USER=vmw_ghost
• GHOST_DATABASE_NAME=vmware_ghost
• GHOST_DATABASE_PASSWORD=dbpassword

To test the deployment of Bitnami Ghost using Helm Chart, you need to have a Kubernetes cluster and kubectl configurated to use that cluster. After that, run the test_helm.sh script. The script already contains a configuration by default so you only need to run:

./test_helm.sh

The report showing the result of the smoke tests execution can be seen in the standard output.

If you'd like to contribute to the project, please send a Pull Request or contact eduriol [at] gmail.com.