search

mattermost / mattermost-docker

Deprecated
Apache License 2.0
964 stars 575 forks source link

web entrypoint: forcefully link existing config #454

Closed potaito closed 4 years ago

potaito commented 4 years ago

When trying to enable SSL, I added the certificate as described here: https://github.com/mattermost/mattermost-docker#install-with-ssl-certificate

However, the web server was still listenting to port 80 instead of port 443 and it took me a moment to see why. The startup output of docker-compose contains this:

web_1  | ln: /etc/nginx/conf.d/mattermost.conf: File exists
web_1  | found certificate and key, linking ssl config

While the second line suggests, that the config mattermost-ssl is being used, the first line tells us, that the linking was not successful, because the symlink already exists from a previous execution. The existing link can be overwritten by adding -f --force to ln.

Related: mattermost#366 (mattermost#366 would probably need to be updated with the same change)

potaito commented 4 years ago

How can I re-run the cla/mattermost check? Force push last commit with new timestamp? :)

cpanato commented 4 years ago

/check-cla