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>
* 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.
Since the only difference is mattermost package and we don't want
to maintain two difference branches, just moved the enterprise version
into a alternative dockerfile
make use of mainline nginx image, switch ssl/non-ssl config file based on presence of cert/key, hardcode app port since it is hardcoded in the app container as well
* Allow config location to be customized from CLI
Config file should be stored in a persistent storage as it is stores the
app status and configuration. It should be independent from container
life cycle and mounted into app container. This commit allows config
location to be changed through CLI. So that when the persistent storage
is mounted, the location can be pointed to the mounted config file.
Also some updates for best practices:
* extracted version numbers in Dockerfile into a environment variable
* Added mattermost/bin to PATH environment variable
* Add customizable environment variables to readme
Now users should create a symbolic link to docker-compose-ssl.yml if
they want to enable SSL or docker-compose-nossl.yml if not.
Rewrite README to describe this rule.
This fixes https://github.com/mattermost/mattermost-docker/issues/5.
Do not copy config.json into /matteronst/config directly because:
> Changes to a data volume will not be included when you update an image.
>
> -- https://docs.docker.com/engine/userguide/dockervolumes/
Instead copy config.template.json into the root and generate
/mattermost/config/config.json from the file.
