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>
I tried to use wal-e as mentioned on dockerhub (see https://hub.docker.com/r/mattermost/mattermost-prod-db). To do the base backup I had to do some additional steps (see https://github.com/mattermost/mattermost-docker/issues/346):
- mount a volume into the database docker container (path in the container is /etc/wal-e.d/env) and put all credentials and the s3 prefix to this folder
- exec into the container and create a superuser (Command: CREATE USER postgres SUPERUSER;)
Now it still fails with the message, that the package *pv* is missing
* Fixes for the smooth deployment of Team edition.
- Just uncommenting out the lines does not work as expected.
- the line for context is required for it to work for team edition deployment.
- Added the subsequent changes in the installation instructions in README.md
* Adding changes as suggested by @ccoenen
- making the changes more clear in the code block
- adding more textual clarity in the sentence on what needs to be changed.
