Deployment documentation updates

source/conf.py

@@ -2392,8 +2392,6 @@ def setup(_: Sphinx):
         "https://docs.mattermost.com/install/install-ubuntu",
 "install/install-ubuntu-2004.html":
         "https://docs.mattermost.com/install/installing-ubuntu-2004-LTS.html",
-"install/install-mmte-helm-gitlab-helm.html":
-        "https://docs.mattermost.com/install/installing-team-edition-helm-chart.html",
 "install/mattermost-omnibus.html":
         "https://docs.mattermost.com/install/installing-mattermost-omnibus.html",
 "install/outbound-proxy.html":
@@ -2547,6 +2545,20 @@ def setup(_: Sphinx):
         "https://docs.mattermost.com/install/install-rhel.html#remove-mattermost",
 "install/install-rhel-8.html#frequently-asked-questions":
         "https://docs.mattermost.com/install/install-rhel.html#frequently-asked-questions",
+"install/install-rhel-8.html#set-the-correct-contexts-for-opt-mattermost":
+        "https://docs.mattermost.com/install/install-rhel.html#set-bin-contexts-for-opt-mattermost-bin",
+"install/install-kubernetes.html#install-mattermost-on-kubernetes":
+        "https://docs.mattermost.com/install/install-kubernetes.html#intended-outcome-and-deployment-recommendations",
+"install/install-kubernetes.html#install-the-operators":
+        "https://docs.mattermost.com/install/install-kubernetes.html#installation-steps",
+"install/install-kubernetes.html#mattermost-cloudnative-bootstrapper-sneak-peek":
+        "https://docs.mattermost.com/install/install-kubernetes.html",
+"install/install-kubernetes.html#does-the-mattermost-operator-replace-the-mattermost-helm-chart":
+        "https://docs.mattermost.com/install/install-kubernetes.html#frequently-asked-questions",
+"install/install-docker.html#deploy-mattermost-on-docker-for-production-use":
+        "https://docs.mattermost.com/install/install-docker.html#deploy-mattermost-on-docker-quick-start",
+"install/install-docker.html#installing-a-different-version-of-mattermost":
+        "https://docs.mattermost.com/install/install-docker.html#install-a-different-version-of-mattermost",
 
 # Integrations redirects.
 # The integrations directory and its contents have been archived in FY23 Q2 and all applicable content has been moved from docs.mm.com to developers.mm.com.

source/configure/calls-deployment.rst

@@ -449,7 +449,7 @@ This is a sample diagram showing how the ``rtcd`` standalone service can be depl
 .. image:: ../images/calls-deployment-kubernetes.png
   :alt: A diagram of calls deployed in a Kubernetes cluster.
 
-If Mattermost isn't deployed in a Kubernetes cluster, and you want to use this deployment type, visit the :ref:`Kubernetes operator guide <install/install-kubernetes:mattermost operator>`.
+If Mattermost isn't deployed in a Kubernetes cluster, and you want to use this deployment type, see the :doc:`Deploy Mattermost on Kubernetes </install/install-kubernetes>` documentation.
 
 Helm Charts
 ~~~~~~~~~~~

source/guides/additional-server-installation-guides.rst

@@ -8,12 +8,10 @@ Additional server installation guides
 
     Deploy Mattermost on Bitnami </install/deploying-team-edition-on-bitnami>
     AWS Elastic Beanstalk Docker setup </install/setting-up-aws-elastic-beanstalk-docker>
-    Install Mattermost Team Edition in GitLab Helm Chart </install/installing-team-edition-helm-chart>
     Open source components </upgrade/open-source-components>
 
 These guides are for administrators looking for alternate deployment methods as well as a list of all open source copmonents included across Mattermost releases.
 
 * :doc:`Deploy Mattermost on Bitnami </install/deploying-team-edition-on-bitnami>`
 * :doc:`AWS Elastic Beanstalk Docker setup </install/setting-up-aws-elastic-beanstalk-docker>`
-* :doc:`Install on GitLab Helm Chart </install/installing-team-edition-helm-chart>`
 * :doc:`Open source components </upgrade/open-source-components>`

source/guides/deployment.rst

@@ -40,7 +40,7 @@ Learn how to install, deploy, and scale Mattermost for teams and organizations o
 * :doc:`Migrate from MySQL to PostgreSQL </deploy/postgres-migration>` - Learn how to migrate from MySQL to PostgreSQL. 
 * :doc:`Prepare your Mattermost database </install/prepare-mattermost-database>` - Learn how to prepare and configure a database for Mattermost.
 * :doc:`Deploy on Ubuntu </install/install-ubuntu>` - Signed packages direct from Mattermost featuring a single command for install and upgrades.
-* :ref:`Deploy using Docker <install/install-docker:deploy mattermost on docker for production use>` - The fastest way to try Mattermost and a great single server installation option.
+* :doc:`Deploy using Docker </install/install-docker>` - The fastest way to try Mattermost and a great single server installation option.
 * :doc:`Deploy with a tarball </install/install-tar>` - Support for any Linux distribution.
 * :doc:`Deploy using Omnibus </install/installing-mattermost-omnibus>` - An entire Mattermost installation on a single server.
 * :doc:`Deploy using Kubernetes </install/install-kubernetes>` - Install using the Mattermost Helm Chart or Operator and simplified updates.

source/install/common-configure-support-email.rst

@@ -0,0 +1,5 @@
+:orphan:
+:nosearch:
+
+.. note::
+    We recommend configuring the `Support Email <https://docs.mattermost.com/administration/config-settings.html#support-email>`_ under ``SupportSettings``, set ``"SupportEmail"``. This is the email address your users will contact when they need help.

source/install/common-default-config-changes.rst

@@ -0,0 +1,8 @@
+:orphan:
+:nosearch:
+
+Configure the following properties in this file:
+
+* Under ``SqlSettings``, set ``DriverName`` to ``"postgres"``. This is the default and recommended database for all Mattermost installations.
+* Under ``SqlSettings``, set ``DataSource`` to ``"postgres://mmuser:<mmuser-password>@<host-name-or-IP>:5432/mattermost?sslmode=disable&connect_timeout=10"`` replacing ``mmuser``, ``<mmuser-password>``, ``<host-name-or-IP>`` and ``mattermost`` with your database name.
+* Under ``ServiceSettings``, set ``"SiteURL"``: The domain name for the Mattermost application (e.g. ``https://mattermost.example.com``).

source/install/common-deploy-faq.rst

@@ -6,11 +6,11 @@
 Why doesn't Mattermost start at system boot?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To have the Mattermost Server start at system boot, the systemd until file needs to be enabled. Run the following command:
+To have the Mattermost Server start at system boot, the systemd unit file needs to be enabled. Run the following command:
 
 .. code-block:: sh
 
-    sudo systemctl enable mattermost.service
+  sudo systemctl enable mattermost.service
 
 Why does Mattermost fail to start at system boot?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -24,8 +24,14 @@ Yes. Mattermost binds to 443 instead of 8065. The Mattermost binary requires the
 
 .. code-block:: sh
 
-    sudo setcap cap_net_bind_service=+ep ./mattermost/bin/mattermost
+  sudo setcap cap_net_bind_service=+ep ./mattermost/bin/mattermost
 
 .. note::
 
-  - We highly recommend using a proxy in front of Mattermost server for up to 200 concurrent users. If you have fewer than 200 concurrent users, you can :doc:`set up TLS </install/setup-tls>`. If you're exceeding 200 concurrent users, you'll need :doc:`a proxy </install/setup-nginx-proxy>`, such as NGINX, in front of Mattermost to manage the traffic.
+  We highly recommend using a proxy in front of Mattermost server for up to 200 concurrent users. If you have fewer than 200 concurrent users, you can :doc:`set up TLS </install/setup-tls>`. If you're exceeding 200 concurrent users, you'll need :doc:`a proxy </install/setup-nginx-proxy>`, such as NGINX, in front of Mattermost to manage the traffic.
+
+Where can I access Mattermost Server logs?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Mattermost Server logs are located in the ``logs`` directory of wherever you installed Mattermost. By default, this is ``/opt/mattermost/logs``, inside the ``mattermost.log`` file.
+

source/install/common-gpg-public-key-changed.rst

@@ -0,0 +1,18 @@
+:orphan:
+:nosearch:
+
+.. important::
+
+  The GPG public key has changed. You can `import the new public key <https://deb.packages.mattermost.com/pubkey.gpg>`_ or run the automatic Mattermost PPA repository setup script provided below. Depending on your setup, additional steps may also be required, particularly for installations that didn't rely on the repository setup script. We recommend deleting the old key from ``/etc/apt/trusted.gpg.d`` before adding the apt repository.
+
+  - For Ubuntu Focal - 20.04 LTS:
+
+    ``sudo apt-key del A1B31D46F0F3A10B02CF2D44F8F2C31744774B28``
+
+    ``curl -sL -o- https://deb.packages.mattermost.com/pubkey.gpg | gpg --dearmor | sudo apt-key add``
+
+  - For Ubuntu Jammy - 22.04 LTS and Ubuntu Noble - 24.04 LTS:
+
+    ``sudo rm /usr/share/keyrings/mattermost-archive-keyring.gpg``
+
+    ``curl -sL -o- https://deb.packages.mattermost.com/pubkey.gpg |  gpg --dearmor | sudo tee /usr/share/keyrings/mattermost-archive-keyring.gpg > /dev/null``

source/install/common-omnibus-tip.rst

@@ -0,0 +1,7 @@
+:orphan:
+:nosearch:
+
+.. tip::
+
+  If you are running the Mattermost Server and database on a single system, we recommend the :doc:`Mattermost Omnibus install method </install/installing-mattermost-omnibus>` as this greatly reduces setup and ongoing maintenance.
+

source/install/common-postgres-database-important.rst

@@ -0,0 +1,6 @@
+:orphan:
+:nosearch:
+
+.. important::
+
+  You need a PostgreSQL database. See the :doc:`database preparation </install/prepare-mattermost-database>` documentation for details on this prerequisite.

source/install/install-docker.rst

@@ -4,48 +4,40 @@ Deploy Mattermost via Docker
 .. include:: ../_static/badges/allplans-selfhosted.rst
   :start-after: :nosearch:
 
+.. important::
+   This deployment method is not recommended for production environments. If you're looking to deploy a production Mattermost instance, we recommend using managed container services like AWS ECS, Azure Container Apps, or Google Cloud Run. These services provide better scalability, reliability, and maintenance features suited for production workloads.
+
 Install Docker
 ---------------
 
-If you don't have Docker installed, follow the instructions below based on your operating system:
+If you don't have Docker installed, follow the instructions below based on your operating system. You'll need `Docker Engine <https://docs.docker.com/engine/install/>`__ and `Docker Compose <https://docs.docker.com/compose/install/>`_ (release 1.28 or later).
 
 .. tab:: macOS
 
-  Install `Docker for Mac <https://docs.docker.com/desktop/setup/install/mac-install/>`_.
+  Follow the `Install Docker Engine on Mac <https://docs.docker.com/desktop/setup/install/mac-install/>`_ documentation.
 
 .. tab:: Windows 10
 
-  Install `Docker for Windows <https://docs.docker.com/desktop/setup/install/windows-install/>`_.
+  Follow the `Install Docker Engine on Windows <https://docs.docker.com/desktop/setup/install/windows-install/>`_ documentation.
 
 .. tab:: Ubuntu
 
-  Follow the `Install Docker Engine on Ubuntu <https://docs.docker.com/engine/install/ubuntu/>`_ documentation, or you can use the Docker package from the Ubuntu repositories:
-
-  .. code-block:: sh
-
-    sudo apt update
-    sudo apt install docker.io
-    sudo systemctl start docker
+  Follow the `Install Docker Engine on Ubuntu <https://docs.docker.com/engine/install/ubuntu/>`_ documentation.
 
 .. tab:: Fedora
 
-  Follow the `Install Docker Engine on Fedora <https://docs.docker.com/engine/install/fedora/>`_ documentation, or you can use the Moby package (Moby is the FOSS upstream project to Docker) from the Fedora repositories:
-
-  .. code-block:: sh
-
-    sudo dnf install moby-engine
-    sudo systemctl start docker
+  Follow the `Install Docker Engine on Fedora <https://docs.docker.com/engine/install/fedora/>`_ documentation.
 
 .. _Deploy Mattermost on Docker:
 
-Deploy Mattermost on Docker for production use
-----------------------------------------------
+Deploy Mattermost on Docker (Quick Start)
+-----------------------------------------
 
-You'll need `Docker Engine <https://docs.docker.com/engine/install/>`__ and `Docker Compose <https://docs.docker.com/compose/install/>`_ (release 1.28 or later).
+This section provides a quick start guide for deploying Mattermost on Docker. Leveraging `Docker Compose <https://docs.docker.com/compose/install/>`_, this deployment solution is designed to get Mattermost up and running quickly. 
 
-.. important::
+.. note::
 
-   - The production configuration results in two separate containers: one for the database and one for the application. An optional third container results when using NGINX for reverse proxy.
+   - The deployment configuration results in two separate containers: a container for the database and a container for the application. An optional third container results when using NGINX for reverse proxy.
    - Encountering issues with your Docker deployment? See the :ref:`Docker deployment troubleshooting <install/troubleshooting:docker deployments>` documentation for details.
 
 To deploy Mattermost on Docker:
@@ -64,8 +56,9 @@ To deploy Mattermost on Docker:
       cp env.example .env
 
 .. important::
-
-      At a minimum, you must edit the ``DOMAIN`` value in the ``.env`` file to correspond to the domain for your Mattermost server.
+
+   - At a minimum, you must edit the ``DOMAIN`` value in the ``.env`` file to correspond to the domain for your Mattermost server.
+   - We recommend configuring the `Support Email <https://docs.mattermost.com/administration/config-settings.html#support-email>`_ via ``MM_SUPPORTSETTINGS_SUPPORTEMAIL``. This is the email address your users will contact when they need help.
 
 3. Create the required directories and set their permissions.
 
@@ -74,7 +67,7 @@ To deploy Mattermost on Docker:
       mkdir -p ./volumes/app/mattermost/{config,data,logs,plugins,client/plugins,bleve-indexes}
       sudo chown -R 2000:2000 ./volumes/app/mattermost
 
-4. Configure TLS for NGINX *(optional)*. If you're not using the included NGINX reverse proxy, you can skip this step.
+4. *(Optional)* Configure TLS for NGINX. If you're not using the included NGINX reverse proxy, you can skip this step.
 
    **If creating a new certificate and key:**
 
@@ -93,32 +86,18 @@ To deploy Mattermost on Docker:
 
    .. code-block:: sh
 
-            mkdir -p ./volumes/web/cert
-            cp <PATH-TO-PRE-EXISTING-CERT>.pem ./volumes/web/cert/cert.pem
-            cp <PATH-TO-PRE-EXISTING-KEY>.pem ./volumes/web/cert/key-no-password.pem
+      mkdir -p ./volumes/web/cert
+      cp <PATH-TO-PRE-EXISTING-CERT>.pem ./volumes/web/cert/cert.pem
+      cp <PATH-TO-PRE-EXISTING-KEY>.pem ./volumes/web/cert/key-no-password.pem
 
    To include the certificate and key, ensure the following lines in your ``.env`` file points to the appropriate files.
 
    .. code-block:: sh
 
-            CERT_PATH=./volumes/web/cert/cert.pem
-            KEY_PATH=./volumes/web/cert/key-no-password.pem
+      CERT_PATH=./volumes/web/cert/cert.pem
+      KEY_PATH=./volumes/web/cert/key-no-password.pem
 
-5. Configure SSO with GitLab *(optional)*. If you want to use SSO with GitLab, and you're using a self-signed certificate, you have to add the PKI chain for your authority. This is required to avoid the ``Token request failed: certificate signed by unknown authority`` error.
-
-   To add the PKI chain, uncomment this line in your ``.env`` file, and ensure it points to your ``pki_chain.pem`` file:
-
-   .. code-block:: sh
-
-      #GITLAB_PKI_CHAIN_PATH=<path_to_your_gitlab_pki>/pki_chain.pem
-
-   Then uncomment this line in your ``docker-compose.yml`` file, and ensure it points to the same ``pki_chain.pem`` file:
-
-   .. code-block:: sh
-
-      # - ${GITLAB_PKI_CHAIN_PATH}:/etc/ssl/certs/pki_chain.pem:ro
-
-6. Deploy Mattermost.
+5. Deploy Mattermost.
 
    **Without using the included NGINX:**
 
@@ -148,18 +127,39 @@ To deploy Mattermost on Docker:
 
       sudo docker compose -f docker-compose.yml -f docker-compose.nginx.yml down
 
-7. Create your first Mattermost system admin user, :doc:`invite more users </collaborate/manage-channel-members>`, and explore the Mattermost platform. 
+6. Create your first Mattermost system admin user, :doc:`invite more users </collaborate/manage-channel-members>`, and explore the Mattermost platform. 
+
+Configure SSO With GitLab (Optional)
+-------------------------------------
+
+If you want to use SSO with GitLab, and you're using a self-signed certificate, you have to add the PKI chain for your authority. This is required to avoid the ``Token request failed: certificate signed by unknown authority`` error.
+
+To add the PKI chain, uncomment this line in your ``.env`` file, and ensure it points to your ``pki_chain.pem`` file:
+
+.. code-block:: sh
+
+   #GITLAB_PKI_CHAIN_PATH=<path_to_your_gitlab_pki>/pki_chain.pem
+
+Then uncomment this line in your ``docker-compose.yml`` file, and ensure it points to the same ``pki_chain.pem`` file:
+
+.. code-block:: sh
+
+   # - ${GITLAB_PKI_CHAIN_PATH}:/etc/ssl/certs/pki_chain.pem:ro
 
 Upgrade from ``mattermost-docker``
 -----------------------------------
 
-The `mattermost-docker <https://github.com/mattermost/mattermost-docker>`__ GitHub repository is deprecated. Visit the `mattermost/docker <https://github.com/mattermost/docker>`_ GitHub repository to access the official Docker deployment solution for Mattermost.
+Visit the `mattermost/docker <https://github.com/mattermost/docker>`_ GitHub repository to access the official Docker deployment solution for Mattermost.
+
+.. note::
+
+   The `mattermost-docker <https://github.com/mattermost/mattermost-docker>`__ GitHub repository is deprecated. 
 
 To migrate from an existing ``mattermost/mattermost-prod-app`` image, we recommend migrating to either ``mattermost/mattermost-enterprise-edition`` or ``mattermost/mattermost-team-edition`` images, which are the official images supported by Mattermost. These images support PostgreSQL 11+ databases, which we know has been a long-running challenge for the community, and you will not lose any features or functionality by moving to these new images.
 
 For additional help or questions, please refer to `this issue <https://github.com/mattermost/mattermost-docker/issues/489>`__.
 
-Installing a different version of Mattermost
+Install a different version of Mattermost
 --------------------------------------------
 
 1. Shut down your deployment.
@@ -170,8 +170,8 @@ Installing a different version of Mattermost
 
 4. Redeploy Mattermost.
 
-Troubleshooting your production deployment
--------------------------------------------
+Troubleshooting deployment
+--------------------------
 
 Docker
 ~~~~~~
@@ -197,7 +197,7 @@ To remove all data and settings for your Mattermost deployment:
 PostgreSQL
 ~~~~~~~~~~~
 
-You can change the Postgres username and/or password (recommended) in the ``.env`` file.
+For quick start deployments, you can change the Postgres username and/or password (recommended) in the ``.env`` file. If your database is managed externally, you'll need to change the password in your database management tool. Then, update the ``.env`` file with the new credentials.
 
 TLS & NGINX
 ~~~~~~~~~~~~
@@ -212,6 +212,6 @@ If you encounter other problems while installing Mattermost, please refer to our
 Trial Mattermost using Docker Preview
 --------------------------------------
 
-Looking to a way to evaluate Mattermost in a non-production environment using Docker? We recommend using the `Mattermost Docker Preview Image <https://github.com/mattermost/mattermost-docker-preview>`_ to install Mattermost in Preview Mode. 
+Looking for a way to evaluate Mattermost in using Docker? We recommend using the `Mattermost Docker Preview Image <https://github.com/mattermost/mattermost-docker-preview>`_ to install Mattermost in Preview Mode. 
 
 See the :doc:`trial Mattermost using Docker </install/trial-mattermost-using-docker>` documentation for details.