Focalboard or Mattermost

[cobordism]

I am a little confused about the relationship between mattermost and focalboard.

Especially in light of the change outlined here: https://github.com/mattermost/focalboard/discussions/4645 I was wondering if this playbook will transition to installing mattermost with the boards plugin or if it will stay with the focalboard "community version".

thanks.

[spantaleev]

It's confusing, because they said they would only support it until April 2023, yet they continue making some new releases including this v7.11.0 prerelease from 5 days ago.

Looks like our version (currently focalboard_version: 7.9.3) is outdated. If you're using Focalboard, you may try adding focalboard_version: 7.11.0 to your vars.yml file and updating. Please confirm if it's OK, so we can bump the version in the ansbile-role-focalboard role repository.

We're not using Focalboard due to it lacking basic features to make it useful, so we can't test upgrades.

---

Otherwise, we have no plans for hosting Mattermost ourselves, but we're open to someone else coming up with a role (based on one of our other roles) and doing a PR for it.

[cobordism]

someone else coming up with a role (based on one of our other roles) and doing a PR for it.

that would be great :)

[cobordism]

If I install mattermost manually (using docker), how can I integrate it with the traefik reverse proxy?

[spantaleev]

By doing these:

• adding the appropriate container labels - you can get inspired from the labels for some of the other services
• connecting it to the traefik container network

[cobordism]

By doing these:

* adding the appropriate container labels - you can get inspired from the labels for some of the other services

* connecting it to the `traefik` container network

can you give me a little help?
I learned that I can add labels in the docker-compose.yml like so:

       traefik.docker.network: "traefik"
       traefik.enable: "true"

Is that what you mean? I also need to specify a Network: tag? should it be "traefik"? should it be set for the container?

I was trying to inspect the containers launched by mash, but it's a bit overwhelming. I wouldn't know where to start.

(for reference, I was doing this: https://docs.mattermost.com/install/install-docker.html#deploy-mattermost-on-docker-for-production-use )

---

or maybe another way: can I manually add another port / servername for trafaek to reverse proxy and manage ssl certificates and I do the rest manually completely independent of mash? I've been trying to get the mattermost docker to integrate with mash but it's too tangled and complex for the uninitiated.