Both zoom and kopano seem to be closed-source + pure commercial solutions and dont have real on-premise solutions… not sure, why they are advertised as alternatives.
big blue button seems to be a major pain, ressource hungry and “not nice” (look at their setup script!), but will likely work…
I had to work that out by myself…
It seems to work pretty well, including fixing your bugs/inconsistencies 
And yes, I expect, that you hate me and will never support my instance…
but: https://git.somenet.org/pub/jan/mattermost_foo.git
i didnt want to be that harsh but that was somewhat my point 
Hi @osieben,
I don’t think there is a way to merge teams, but you could move channels from one team to another with this CLI command: https://docs.mattermost.com/administration/command-line-tools.html#mattermost-channel-move.
Hope this helps,
Thank you for the feedback @jasondaigo and @someone !
For Kopano, there are source files available in the links below
I’d be curious to hear more about BigBlueButton - in terms of resource usage and other concerns you may have.
We’d also be open to working with our community to create a WebRTC plugin for Mattermost if there is interest on such a plugin!
I am deploying from the helm chart here:
It uses this image here:
https://hub.docker.com/r/mattermost/mattermost-team-edition
Both clearly say team edition, and in the values file there is no config flag to select team edition. When I deploy though I see this in the logs: {“level”:“info”,“ts”:1552325998.6409657,“caller”:“app/server.go:195”,“msg”:“Enterprise Enabled: true”}
How do I set this to false? I checked my values, and I don’t appear to have enabled any Enterprise features.
Any help would be greatly appreciated.
Hi, @osieben
While there is no official feature available to merge teams together by default as mentioned by @amy.blais , I came across the following Java app that might work, though the code has been around since 2016. Perhaps you can give it a try on a staging instance to see if it is still applicable on your end:
Take note that this method is unofficially supported, so please read the code before you proceed.
Hello, @bcxxbc
Before digging deeper into this matter, can I please check if you went through the steps explained in the How to install Mattermost Team Edition Helm Chart in GitLab Helm Chart deployment, especially on the deployment part here?
helm upgrade --install --name mattermost -f values.yaml stable/mattermost-team-edition
For the record, I have the same line on my logs when I deployed my team edition on Ubuntu 16.04 as well. So, I would think that the full enterprise features is tied to the license key purchased though the logs show that the Enterprise Enabled parameter is enabled to true:
ahmaddanialmohammad@ubuntu:/opt/mattermost/logs$ cat mattermost.log | grep "Enterprise Enabled: true" | wc -l
544
I will check with the team if that is the case. As of now, can you confirm if the Mattermost deployment is running properly on your end nevertheless?
Hi, @talksonweb
I had this tested on my end and I was able to make it work by specifying the Content-Type header to application/json and set the Body content to Raw as per the screen shot that you can see below:
As a result, you can see that the message was sent successfully:
Can you please give it a try on your end and let me know how it goes? Thanks.
Cool. But why smb and not nfs?
I cannot start the mattermost container on Ubuntu. The container gives error and stays forever in restarting
Version 5.7.0.
OS: Ubuntu 18.10
docker-compose.yml:
version: ‘3’
services:
mattermost:
image: “mattermost/mattermost-preview”
restart: “always”
container_name: intranet_mattermost
ports:
- 8065:8065
networks:
- devIntranet
networks:
devIntranet:
Starting the service using command
docker-compose up -d
Access the mattermost via web browser and API via cURL by accessing the url http://192.168.240.59:8065/ (my IP)
Using docker ps:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
34de84443068 mattermost/mattermost-preview “/bin/sh -c ./docker…” About an hour ago Restarting (127) 41 seconds ago intranet_mattermost
Using docker logs --tail 50 --follow --timestamps mattermost-preview:
2019-03-11T21:05:50.265431030Z Starting platform
2019-03-11T21:05:50.265645376Z ./docker-entry.sh: line 18: /mm/mattermost/bin/mattermost: No such file or directory
When I try to enter the container using the command docker exec -it mattermost-preview /bin/bash, I am ejected from the container and when I try to access again, I get the following error (because the container is already restarting)
Error response from daemon: Container b15fd76ac44aad39ec74f4b5c1e7d8b7b6a22ea9aec4b56458dd4cebc7f62561 is not running
Thanks so much, @amy.blais
Different Teams can see all other Mattermost members via “Add new members to team” link. Even worse they can even add other teams members as regular user.
Mattermost 5.8.
Create 2 different teams.
Create a few testaccounts on said teams.
Login with one Testuser.
Click Add members to team.
ALL Users are visible as non privileged user.
ALL User can be invited as non privileged user.
Teams are meant to seperate Accounts.
A regular User should not have the privilege to see all other server members nor to invite them.
ALL Users are visible as non privileged user.
ALL User can be invited as non privileged user.
Hi @Betriebsrat,
If you want a team to be private, please go to Team Settings > Allow anyone to join this team > No.
More information about team settings is here: https://docs.mattermost.com/help/settings/team-settings.html.
There are additional team permissions settings in Enterprise Edition: https://docs.mattermost.com/deployment/advanced-permissions.html#team-override-scheme-e20.
Found this issue as I was having the same problem on my Synology DS918+. The error is on the line
addgroup -g ${PGID} mattermost
&& adduser -D -u ${PUID} -G mattermost
I replaced the variables with the hard coded values from the ARG declaration. I don’t know what causes the error, perhaps an old Docker version on the Synology (17.05). Either way - by replacing with static values I got it running.
So, this works,
addgroup -g 2000 mattermost
&& adduser -D -u 2000 -G mattermost
hi,
thank you but said setting is already set in my test env.
This does NOT prevent a regular user to invite anyone else.
The issue for me is already that teams see each other members, this should not be the case in my opinion, since they are on different teams for a reason.
Hi @Betriebsrat,
Preventing regular users from inviting others to a team can be done with the Enterprise permissions settings.
I will ask our team about the issue of being able to see all members on a server when adding new members to a team, but I’m guessing this would be a “feature request” to change this behaviour.
what is the point of teamadmins then for the team edition?
what is the point of creating teams in the first place then, when everybody can do everything basically.
pardon me but that feels like killing basic features to force people into enterprise.
This is with the wonka colors (https://github.com/nightsense/wonka)
{
"sidebarBg":"#f0e6dd",
"sidebarText":"#2b241d",
"sidebarUnreadText":"#468dd4",
"sidebarTextHoverBg":"#fff7f0",
"sidebarTextActiveBorder":"#ab8e38",
"sidebarTextActiveColor":"#ab8e38",
"sidebarHeaderBg":"#b5aca3",
"sidebarHeaderTextColor":"#2b241d",
"onlineIndicator":"#a2ec14",
"awayIndicator":"#dcbd4e",
"dndIndicator":"#fd0000",
"mentionBj":"#a26fbf",
"mentionColor":"#ffffff",
"centerChannelBg":"#fff7f0",
"centerChannelColor":"#2b241d",
"newMessageSeparator":"#ff8800",
"linkColor":"#d4ac35",
"buttonBg":"#d4ac35",
"buttonColor":"#ffffff",
"errorTextColor":"#a94442",
"mentionHighlightBg":"#f0e6dd",
"mentionHighlightLink":"#3b332c",
"codeTheme":"solarized-light",
"mentionBg":"#a26fbf"
}