Plugin uploads, local mode, and HTTPS are enabled by default. These settings are modified in the
yaml file as described below.
With Mattermost Omnibus, the
config.json file is no longer used as Omnibus stores the Mattermost configuration in the database. The Omnibus platform itself requires of a configuration of its own, that is stored in
/etc/mattermost/mmomni.yml. This file contains the data that Omnibus needs to configure the platform and connect all the services together. So you’ll need to use mmctl to make changes to your Mattermost server configuration using
mmctl --local config edit.
For Omnibus to work properly, there are some configuration parameters that are fixed and cannot be changed through the web interface - for example, the port that Mattermost uses to run. Other parameters need to be configured directly in the
mmomni.yml file instead of in the Mattermost web interface or the
The properties that you can configure in this file are:
db_user: The PostgreSQL database user. This value is generated during the Omnibus installation and should not be changed.
db_password: The PostgreSQL database password. This value is generated during the Omnibus installation and should not be changed.
fqdn: The domain name for the Mattermost application. This is the value that is asked during the install process, and it’s used to populate the
ServiceSettings.SiteURLMattermost configuration property, as well as to retrieve and configure the SSL certificate for the server.
https: This indicates whether the platform should be configured to use HTTPS or HTTP with values
false. The recommended way to install Mattermost is to use HTTPS, but you can disable it if required.
data_directory: This is the directory where Mattermost stores its data.
enable_plugin_uploads: This setting can be
falseand is used to configure the
PluginSettings.EnableUploadsMattermost configuration property.
enable_local_mode: This setting can be
falseand is used to configure the
ServiceSettings.EnableLocalModeMattermost configuration property.
nginx_template: Optional path to a custom NGINX template.
After modifying the
mmomni.yml configuration file, you need to run
mmomni reconfigure for Omnibus to apply the changes and restart Mattermost.
Mattermost Omnibus generates an
nginx configuration depending on how the different properties of the
mmomni.yml file are set. However, you may need to customize the configuration further to support other use cases, such as using custom SSL certificates. For those cases, Omnibus supports using a custom
nginx template to generate its configuration.
To use this feature, you need to copy and modify the original template located at
/opt/mattermost/mmomni/ansible/playbooks/mattermost.conf to a new location. Then, you can either use the variables and internal logic already bundled in the template and modify the parts that you need, or use a fully static configuration instead.
After the template has been customized, add an
nginx_template property to the
/etc/mattermost/mmomni.yml configuration file, and then run
mmomni reconfigure. The reconfigure process will use the new template to generate the NGINX final configuration. You can check the contents of the
/etc/nginx/conf.d/mattermost.conf file to validate that the changes were applied successfully.
Please be careful when using this feature, as making changes to the custom template can cause the reconfigure process to fail, or the generated NGINX configuration to be invalid.
This feature is available from Mattermost Omnibus version 5.32.0.
If you wish to remove Mattermost and Mattermost Omnibus completely for any reason, you can run this command:
sudo apt remove --purge mattermost mattermost-omnibus
Mattermost Omnibus includes a CLI tool:
mmomni, which is used to manage configuration.
Server and domain migration as well as backup and restore is now much easier - you can take snapshots of all content in your Mattermost server. This includes all content, users, plugins, configurations, and databases. You can restore on the same server or move to another server at any time.
mmomni backup -o /tmp/Aug27-2020.tgz
mmomni restore /tmp/Aug27-2020.tgz and
Future releases may include automation for snapshot management.
mmomni backup: Takes a complete snapshot of your Mattermost server and places the backup file in a specified file location.
mmomni restore: Restores specified backup file to your Mattermost server.
mmomni reconfigure: Reruns the process that changes domain, SSL, or any Omnibus-specified restrictions such as the ability to upload plugins. It also applies any changes made to the
mmomni status: Shows current status of all Omnibus components.
mmomni tail: Runs a join tail of logs of all Omnibus components.
Although the recommended way to install and configure Omnibus is with SSL enabled, if you want to use or test without it, you can run:
sudo MMO_HTTPS=false apt install mattermost-omnibus
Mattermost Omnibus stores the configuration of the Mattermost server into the database. You can edit your config by running the following mmctl command after connecting mmctl to the instance:
mmctl config edit. If you’re logged into the machine as the
mattermost user, you can use
mmctl --local config edit as well.
Yes! We are planning several packages and currently seeking feedback to help us prioritize these.
Yes! We are currently seeking feedback to help us prioritize these.
MySQL is not supported. Omnibus is architected to run with PostgreSQL.
Yes. Mattermost Omnibus bundles the free, unlicensed Mattermost Enterprise Edition, and Enterprise features are unlocked when you purchase and upload a license.
No, Omnibus is designed to be a self-contained Mattermost platform, so it expects all the necessary components to be in the same server.
Yes. The SSL certificate automatically updated and renewed. Omnibus installs the certbot package to manage the certificate, and it comes with a cron job that you can find at /etc/cron.d/certbot that automatically launches the renewal process.
If you have any problems installing Mattermost Omnibus, see the troubleshooting guide for common error messages, or join the Mattermost user community for troubleshooting help.