mantisbt-docker
Docker image for Mantis Bug Tracker https://www.mantisbt.org/
Why this image?
There are some other alternative images exist already such as vimagick/mantisbt or mikroways/mantisbt. Why do we need yet another image?
Answer is - those images don't have all the nice features :)
- Always latest MantisBT version.
 - Comes with the latest PHP version (7.4 as for today)
 - Allows to easily configure presence of 
adminservice folder - Comes with built-in integration with Gitlab and Github source plugins
 - Example 
docker-compose.ymlfile provided for getting started in one click! 
Quick start
- Download 
docker-compose - Check the environment variables (at least you need to set MASTER_SALT env variable, doc)
 docker-compose up -d- Open browser at 
localhost:8989/admin/install.phpand follow installation instructions (TODO: DB credentiasl) -- IgnoreConfig File Exists but Database does notwarning and proceed installation - Log in as 
administrator/root(default credentials) and confugre whatever you need (typically you want to create your own Admin user and disable built-in "administrator" first) - Check MantisBT own's checks at 
localhost:8989/admin/. Note: several warnings are expected to be "WARN" due to issues in MantisBT, such as magic quotes warning (#26964 and "folder outside of web root" warnings (#21584)) - When ready to move to production, either remove 
MANTIS_ENABLE_ADMINenv variable or set it to 0 - this will remove "admin" folder from the installation. 
For further details refer to official documentation
Extensions
Custom config settings
If you need to customize more options in config, create config_inc_addon.php file and mount it to /var/www/html/config/config_inc_addon.php in container. This fill will be added to default config_inc.php. Mounting it will allow you to see the changes instantly without rebuilding/restarting the container.
There are following env variables supported:
- EMAIL_WEBMASTER - maps to 
g_webmaster_email - EMAIL_FROM - maps to 
g_from_email - EMAIL_RETURN_PATH - maps to 
g_return_path_email 
More details are available in documentation section
Custom plugins
In order to add your own custom plugins into the image, either create your own Dockerfile and copy extra plugins to /var/www/html/plugins/ or add volume in docker-compose to mount extra plugin directly inside existing image ./custom_plugin/:/var/www/html/plugins/custom_plugin/