-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment Section Restructure [WIP] #7816
base: master
Are you sure you want to change the base?
Conversation
Newest code from mattermost has been published to preview environment for Git SHA 7d972f9 |
Newest code from mattermost has been published to preview environment for Git SHA 53ed7b9 |
Newest code from mattermost has been published to preview environment for Git SHA 3156681 |
Newest code from mattermost has been published to preview environment for Git SHA 17dac6e |
Newest code from mattermost has been published to preview environment for Git SHA 749e62b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! I like the guided approach to helping admins choose the right deployment method for their use case.
|
||
**System Extensions** | ||
|
||
Mattermost is not only a collaboration tool but also a platform designed for extensibility. Key extensibility features include: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we mention SAML and LDAP here? For most enterprises, these are keen system to integrate.
ALTER DATABASE mattermost OWNER TO mmuser; | ||
GRANT USAGE, CREATE ON SCHEMA PUBLIC TO mmuser; | ||
|
||
3. Configure PostgreSQL for remote connections (if database is on a separate server): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should make it more clear that this only needs to be done if the DB is not on the same server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you looking for something more than just:
(if database is on a separate server)
|
||
.. code-block:: sh | ||
|
||
sudo chown -R mattermost:mattermost /opt/mattermost/data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did the admin already create the mattermost
account by this point in the guide?
- Application ports: 80/443 (TCP) for HTTP/HTTPS | ||
- Database port: 5432 (TCP) for PostgreSQL | ||
- SMTP port: 10025 (TCP/UDP) for outbound email |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make it clearer which are outgoing and which are incoming connections?
.. 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. | ||
- This deployment method isn't recommended for production environments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the downsides of a docker deployment vs a tarball one? As a matter of fact, there are a lot of Docker deployments out there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a thread here: https://hub.mattermost.com/private-core/pl/3zey5kaq7bgtibpqoza4ujw36h discussing this
|
||
The Mattermost desktop application is available for Windows, macOS, and Linux operating systems. Learn about installation, configuration, and management options for deploying the desktop app in your environment. | ||
|
||
This documentation provides guidance on deploying and managing the Mattermost Desktop application across your organization. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All these detailed guides are great, but I wonder if we also should have a "vanilla" one.
What should an admin do if they want to roll out the desktop in their org? What installers exists?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree
System requirements | ||
-------------------- | ||
|
||
Ensure your system meets these minimum requirements: | ||
|
||
- Operating System: 64-bit Linux distribution | ||
- Hardware: 1 vCPU/core with 2GB RAM (supports up to 1,000 users) | ||
- Storage: Minimum 10GB available space | ||
- Database: PostgreSQL v13+ | ||
- Network: Reliable internet connection with sufficient bandwidth |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have more detailed guidelines on the system requirements in the new docs? In the old version, there was a handy page with the suggested resources (https://docs.mattermost.com/scale/scaling-for-enterprise.html). Does that still exist?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does still exist, yes. And I agree that we'll need to connect our deployment guidance to our scaling guidance
@nickmisasi - Can I get your help answering @hanzei's inline questions, please? |
@cwarnermm I have answered what I can. @DSchalla will probably be better to answer the rest as he's got a more holistic view of the changes in this PR |
Newest code from mattermost has been published to preview environment for Git SHA 24604f8 |
Newest code from mattermost has been published to preview environment for Git SHA e52224c |
Newest code from mattermost has been published to preview environment for Git SHA ed05ee4 |
Newest code from mattermost has been published to preview environment for Git SHA 76cdd88 |
Newest code from mattermost has been published to preview environment for Git SHA 4c8b30b |
Newest code from mattermost has been published to preview environment for Git SHA 946d2c8 |
Newest code from mattermost has been published to preview environment for Git SHA 8ac664a |
Newest code from mattermost has been published to preview environment for Git SHA b7699ac |
Summary
(NOTE: This is still a work in progress, with the same placeholders in place and content missing from the previous structure that must be carried over.)