App service
Services/Mattermost

Mattermost service

Self-hosted Mattermost Team Edition service for team messaging, with persistent file storage and a linked PostgreSQL database.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

On Wodby

How Mattermost runs on Wodby

What Wodby sets up for Mattermost on this service. Mattermost runs from the official mattermost/mattermost-team-edition image. Configuration is passed as MM_<SECTION>_<SETTING> environment variables, which take precedence over config.json; a setting given by a variable cannot be changed in the System Console.

Linked services

LinkVariables
PostgreSQL (required)MM_SQLSETTINGS_DRIVERNAME, MM_SQLSETTINGS_DATASOURCE
SMTP server (optional)MM_EMAILSETTINGS_SMTPSERVER, MM_EMAILSETTINGS_SMTPPORT, MM_EMAILSETTINGS_ENABLESMTPAUTH, MM_EMAILSETTINGS_CONNECTIONSECURITY

Mail goes to the linked mail service without authentication or connection security. The mail variables are present only while the link exists.

What the manifest sets

  • MM_SERVICESETTINGS_SITEURL is the environment's primary URL.
  • MM_FILESETTINGS_MAXFILESIZE (100 MB) is the only upload limit; the route passes request bodies through without a size limit and has no request timeout. Setting the route's request_body_size would buffer every request in the gateway and break the WebSocket connection.
  • Logs go to the console as JSON (MM_LOGSETTINGS_*); file logging is off.
  • MM_CONFIG points to /mattermost/config/config.json. Before the first start an init container creates that file with initial plugin states, only when it does not exist.
  • The container runs as user and group 2000 and listens on port 8065. The health endpoint is /api/v4/system/ping.

Changing configuration

Settings that the manifest or a link provides as variables are changed on the service (environment variables) and applied by a deployment. Other settings can be changed in the System Console; they are saved to config.json on the volume.

Data

One data volume holds four directories:

Path in the containerContent
/mattermost/datauploaded files
/mattermost/configconfig.json
/mattermost/pluginsserver plugins
/mattermost/client/pluginsweb application plugins

Everything else is in the linked PostgreSQL database. The manifest declares no backup, import or action for this service, and creates no account: the first system administrator is created in the browser.

Overview

Technical profile and packaging

This page shows how Mattermost is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

11.7

Ports and protocols

8065/HTTP

Labels

mattermost

Persistent volumes

Mattermost data

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Mattermost as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

8065/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Volumes

Mattermost data

Service links

These links define which other services can connect to Mattermost when it is used inside a stack.