* be consistent with the use of tabs
* tabs; shellcheck; consistency
* use tabs
* use shellcheck to fix non POSIX stuff
* be consistent with the use of quotes and if-then-else / for-do-done
#### Context:
Right now, multiple sources point to the server binaries on releases.mattermost.com, including the download page, upgrade instructions, Helm charts, version archive, and others.
We can identify the download source by adding a querystring to the url, i.e. https://releases.mattermost.com/5.22.1/mattermost-5.22.1-linux-amd64.tar.gz?src=docker-app
The intent is that we can then identify sources of downloads, identify those that typically lead to an unsuccessful server activation, and improve the experience for the developer/administrator.
This PR adds the "?src=docker-app" querysting tag to download source for the Docker app, so we know when someone downloaded it from this source
See https://github.com/mattermost/docs/pull/3596 for a similar change made to download sources on the version archive page.
Currently the command `docker-compose build` throws an error for building the database because it uses an old pip version.
This PR updates pip right before it is called. Anyways this should just be a temporary fix because the image uses Python 2.7 wich out of support since Jan 2020
currently, if you follow the instructions and uncomment the lines, you
will get a YAML error:
```
ERROR: yaml.parser.ParserError: while parsing a block mapping
in "./docker-compose.yml", line 23, column 5
expected <block end>, but found '<block mapping start>'
in "./docker-compose.yml", line 25, column 7
```
found the potential solution in mattermost/mattermost-docker#343
Co-authored-by: mattermod <mattermod@users.noreply.github.com>
In this commit I'm adding some logic to ensure that the `entrypoint.sh`
file handles a pre-existing `mattermost.conf` file within the nginx
folder.
During deployment of some more custom nginx configuration it was
noticed that the linking process fails, because a file already exists
with the filesystem.
Signed-off-by: Akendo <akendo@akendo.eu>
