You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For further details refer to [official documentation](https://www.mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.install.new)
36
36
37
-
# Example docker-compose.yml
37
+
##Example docker-compose.yml
38
38
39
39
```YAML
40
40
version: "3"
@@ -54,6 +54,12 @@ services:
54
54
- EMAIL_WEBMASTER=webmaster@localhost
55
55
- EMAIL_FROM=webmaster@localhost
56
56
- EMAIL_RETURN_PATH=webmaster@localhost
57
+
# SMTP Settings, below are default values
58
+
#- SMTP_HOST=smtp.yourmail.com
59
+
#- SMTP_USER=username
60
+
#- SMTP_PASSWORD=superstrongpassword
61
+
#- SMTP_PORT=587
62
+
#- SMTP_MODE=tls # Maps to $g_smtp_connection_mode, defaults to tls, can be ssl or empty
57
63
# Uncomment only if modified from default values
58
64
#- MYSQL_HOST=db
59
65
#- MYSQL_DATABASE=bugtracker
@@ -64,10 +70,10 @@ services:
64
70
restart: always
65
71
66
72
db:
67
-
image: mysql:5.7
73
+
image: mysql:8.4
68
74
container_name: mantis_db
69
75
volumes:
70
-
- ./db_data:/var/lib/mysql
76
+
- ./db_data_v8:/var/lib/mysql
71
77
environment:
72
78
- MYSQL_ROOT_PASSWORD=root
73
79
- MYSQL_DATABASE=bugtracker
@@ -77,6 +83,30 @@ services:
77
83
78
84
```
79
85
86
+
## Upgrading
87
+
88
+
Normally, you should be able to upgrade freely without any restrictions, just make sure to run the compose with `MANTIS_ENABLE_ADMIN=1` after updating the versions and go to `your-mantis-instance/admin` to perform database upgrades when needed. That's all :)
89
+
90
+
### MySQL 5.7 EOL
91
+
92
+
`docker-compose.yaml` file before May 2025 in this repo was using `mysql:5.7` as database container. This has became EOL in 2023, so it was updated to current LTS version 8.4. Unfortunately [MySQL does NOT support direct upgrade](https://dev.mysql.com/doc/refman/8.4/en/upgrade-paths.html), so the recommended way is to just backup the database, upgrade the version and set new path for `db_data`, then recreate the database from dump.
- EMAIL_RETURN_PATH - maps to `g_return_path_email`
138
+
-`EMAIL_WEBMASTER` - maps to `g_webmaster_email`
139
+
-`EMAIL_FROM` - maps to `g_from_email`
140
+
-`EMAIL_RETURN_PATH` - maps to `g_return_path_email`
141
+
-`EMAIL_FROM_NAME` - maps to `$g_from_name`
142
+
143
+
Also SMTP env variables are supported as well:
144
+
145
+
-`SMTP_HOST=smtp.yourmail.com`
146
+
-`SMTP_USER=username`
147
+
-`SMTP_PASSWORD=superstrongpassword`
148
+
-`SMTP_PORT=587`
149
+
-`SMTP_MODE=tls` - Maps to $g_smtp_connection_mode, defaults to tls, can be ssl or empty
150
+
```
111
151
112
-
Those are good enough to start with. Going further, to configure SMTP you might need to create custom config (as described above) with the values like:
152
+
Those are good enough to start with. Going further, to configure more details you might need to create custom config (as described above) with the values like those:
0 commit comments