I'm getting the below. This seems to be the solution, though I think that needs to be done in the docker file build?
Also, there doesn't seem to be a way to persist the config, unless that's the data volume you mention - which is possibly just because the above error causes my docker to crash before it can write it. Thought I'd check here in case you can shed any light. The below is my full log, very short so very easy!
Initializing mattermost...
Initializing datadir...
Initializing logdir...
Installing configuration templates...
Configuring mattermost...
Configuring mattermost database...
Configuring SMTP...
Configuring GitLab...
[MySQL] 2020/04/07 05:37:14 packets.go:32: EOF
[MySQL] 2020/04/07 05:37:14 packets.go:32: EOF
[MySQL] 2020/04/07 05:37:14 packets.go:32: EOF
I'm guessing that I can just disable gitlab if I don't need it, or create an account and maybe that resolves this issue - any idea what docker variable disables gitlab?
I'm getting the below. This seems to be the solution, though I think that needs to be done in the docker file build?
Also, there doesn't seem to be a way to persist the config, unless that's the data volume you mention - which is possibly just because the above error causes my docker to crash before it can write it. Thought I'd check here in case you can shed any light. The below is my full log, very short so very easy!
Initializing mattermost...
Initializing datadir...
Initializing logdir...
Installing configuration templates...
Configuring mattermost...
Configuring mattermost database...
Configuring SMTP...
Configuring GitLab...
[MySQL] 2020/04/07 05:37:14 packets.go:32: EOF
[MySQL] 2020/04/07 05:37:14 packets.go:32: EOF
[MySQL] 2020/04/07 05:37:14 packets.go:32: EOF
I'm guessing that I can just disable gitlab if I don't need it, or create an account and maybe that resolves this issue - any idea what docker variable disables gitlab?