Ability to run Mattermost on Windows Server
- Producing a version of Mattermost that runs on Windows Server
- Providing install guide for Windows Server
- Fixing issues with config.json not rendering in Notepad
- Offering .zip download for Windows rather than tar
MikeBee
shared this idea
Huge thanks to Jared Shields for drafting the production install guide for Window Server and helping make the Windows version straight forward to install: https://docs.mattermost.com/install/prod-windows-2012.html
Several changes were needed, such as making config.json readable in Notepad, changing from tar file to .zip which Windows can open natively without installing 3rd party decompression apps.
We’ve updated the original request to make this about having the ability to run Mattermost on Windows Server, which is about providing a Windows binary with each release, which enables a sort of “Mattermost Windows Server User Group” to become available, providing peer-to-peer support for Windows releases.
Mattermost on Windows Server is available. It’s less mature than Linux right now and as it grows in popularity, we need to be clear to the community on status of vetting and support.
Specifically:
1. Need a meta-ticket to update Mattermost documentation to distinguish between multiple binaries
Software and Hardware requirements, upgrade guide, migration guide, backup guide, Mattermost Load Test, etc. all assume Linux binary and we’d need to add small tweaks to be clear these are for the Linux version of Mattermost
2. Need to define levels of quality and support
There’s a growing number of features in Mattermost that aren’t yet official, e.g. WebRTC, Debian install, link previews, and now Windows Server support. We need to define quality levels (e.g. experimental, alpha, beta, official?) and support levels (e.g. peer-to-peer vs. included in Mattermost, Inc. SLAs)
3. Update TOC in docs
Once we have a system for declaring levels of quality and support for different features, we should probably review the docs TOC to make things easier to find—right now we kind of “hide” the features that are in development, but it would make more sense to make them more prominent with the proper definitions.
This is a really wonderful step to expand what Mattermost can do, and bring in an whole new community of users. We want to make sure things are done the right way.
-
Jared Shields
commented
Hey everyone! There's an unofficial windows installation guide available. My team is running it with no problems. Have a look at the guide, and if you have any feedback, please let me or the MM team know. Greatly appreciate it!
The guide can be found here: https://docs.mattermost.com/install/prod-windows-2012.html
Comments/Issues on the guide can be posted here: https://github.com/mattermost/docs/issues/360
-
Andrey
commented
The mentioned method with replacing "linux" with "windows" does work for all the links up to version 3.4.0, thanks!
Unfortunately this does not work with 3.5.1. Anyone have any other hacks in mind?
-
MikeBee
commented
Excellent. Replacing 'linux' for 'windows' in the download link works - thanks Jared!
-
Anonymous
commented
Nice, that windows download does work. So seems they are working on it?
-
Jared Shields
commented
@all - Im running MM on windows with no problems at all. Replace "Linux" in the release download link with "windows" and you'll get a package fully built for windows. Extract it and run it... No issues. I wrapped platform.exe with a tool so it would launch as a service and it's working with no issues what so ever. Literally plug and play, no building required. Shoot me an email if you have any questions.
-
William Laffin
commented
@Craig Windows VMs are mandatory where I am at; so a vm inside a vm is a non-starter. As well; mattermost works just fine on windows; there just needs to be instructions...What I did:
1. open the dev docker and download that tarball. (this has the react dist already built)
2. install mysql with the user/password in the dev docker.
3. Install go for windows
4. install git for windows
5. go get github.com/mattermost/platform; copy that bin created into the bin folder of the tarball replacing the linux binary.
6. from within mattermost dir; run bin\platform
(I added an if runtime = os then switch slashes after finding absolute dir; not sure this was necessary; the issue i did that for was that 2.1 vs github uses different directories for dist/template) -
Craig Engbrecht - Broked Computer Inc.
commented
Not to be rude. I am curious more why you would want to run anything more than a test bench on windows. As its open source, I am sure that you could run a Linux VM to control this server, and host the apache, and Posgres server?
P.s. You can run Apache and Posgres on windows, even mySQL, which is 90% of what's needed.