-
Notifications
You must be signed in to change notification settings - Fork 264
Update env.example #120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Update env.example #120
Conversation
| ## This will be 'mattermost-enterprise-edition' or 'mattermost-team-edition' based on the version of Mattermost you're installing. | ||
| MATTERMOST_IMAGE=mattermost-enterprise-edition | ||
| MATTERMOST_IMAGE_TAG=7.1 | ||
| MATTERMOST_IMAGE_TAG=latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure that is fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel like a one-fits-all script is the way to go. To get Mattermost running, you only need the docker compose file, and that is it. People might prefer other ways to install docker compose, e.g. via their package manager.
|
It's bad practice to use a latest on prod |
|
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
Could we always use the latest docker image?