Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I've added preliminary support for SmartOS / Solaris! This is interesting for people who want to run Mattermost on the Joyent Public Cloud (or private cloud with Triton like we do) or just on SmartOS.
Mattermost just works on SmartOS however fsnotify doesn't have support for FEN (The Solaris equivelant of Linux inotify). This leads to spamming of logs. There is actually an pull request open for FEN support in fsnotify (fsnotify/fsnotify#196). However this is not yet merged and also this code (unlike Linux, Windows and Darwin support) will only compile on Solaris. Which is kinda of a bummer for cross compiling. I think the the hot-swapping of templates is only done during development? Therefor I thought it would be better to just not support hot-template-reloading on Solaris and any other OS fsnotify might not support. It's just not worth the trouble of breaking cross compilation. I wanted to also add some documentation to make it obvious the Solaris build doesn't support hot-swapping templates but I couldn't find any documentation regarding template hot-swapping (so there was nothing to modify).
Ticket Link
I tried to create a Jira account so I could create a JIRA issue (as per procedure) but logging in to Atlassian cloud proved troublesom. I couldn't login with GitHub (only Google). I then tried to create an account and apparently I already had one so I tried to reset my password. That lead to an E-Mail with a link which displayed the following error when I clicked on it:
Illegal request-target, unexpected character '=' at position 471
. No idea what it is but it seems like a nice attack vector ;-). Anywho at that point I gave up trying to create a JIRA ticket.Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]