Can't run mattermost with data in non-standard path - mattermost['home'] ignored?
I'm using gitlab-ce-8.14.2-ce.0.el6.x86_64 on a managed VM running RHEL6. For reasons, data has to be stored in /var/local/gitlab
instead of the default /var/opt/gitlab
.
I've changed this everywhere in gitlab.rb
:
user['home'] = "/var/local/gitlab"
...
mattermost['home'] = '/var/local/gitlab/mattermost'
also reflected in gitlab-ctl show-config:
"mattermost": {
"enable": true,
"home": "/var/local/gitlab/mattermost",
...
```
For gitlab it works fine. But mattermost doesn't start because it still looks for its `config.json` file in` /var/opt` instead of `/var/local`:
```
2016-12-02_12:17:37.56736 [13:17:37 CET 2016/12/02] [EROR] (main.main:107) Unable to load mattermost configuration file: Error opening config file=/var/opt/gitlab/mattermost/config.json, err=open /var/opt/gitlab/mattermost/config.json: no such file or directory
```
What I have found is that the mattermost service script **`/opt/gitlab/sv/mattermost/run`** contains the reference to the invalid path that is causing the problem:
#!/bin/sh exec 2>&1 cd /opt/gitlab/embedded/service/mattermost exec chpst -P -U mattermost -u mattermost /opt/gitlab/embedded/bin/mattermost -config /var/opt/gitlab/mattermost/config.json
Without knowing much about omnibus internals I suspect this is a bug where the config path in the mattermost run script does not get updated correctly according to the config in `gitlab.rb`.
Or am I overlooking something?
This has been happening on a fresh gitlab-ce 8.13 install and is still persisting after an update to 8.14.