Skip to content
Learn more about Mattermost for Microsoft Teams »

I suggest you ...

← General

Install Mattermost in a Subdirectory

We are using HAProxy and multiple subdirectories as internal redirects, to consolidate services.

Right now, Mattermost assumes it is being install at the root of a fully qualified domain name, so moving it anywhere breaks multiple paths for many files.

It would be much more valuable for teams to be able to deploy to "http://www.example.com/chat" instead of always resorting to "http://chat.example.com/".

See: https://mattermost.atlassian.net/browse/PLT-200

213 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Anthony Lavado shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • An3s commented  ·   ·  Report

    When running an NGINX reverse proxy server in front of Mattermost, and the latter being set up to exist in a subdirectory, how then should the NGINX config - as documented e.g. here https://docs.mattermost.com/install/install-rhel-7.html#configuring-nginx-as-a-proxy-for-mattermost-server - be modified to match the extra directory level?
    I believe I have the regular "location /" stansa properly modified, but I'm not sure on how to modify the "location ~ /api/..." stansa.
    I would like to suggest to add a separate example to the docs, specifically for the subdirectory-case. Thanks for any pointers!

  • MarkMaldaba commented  ·   ·  Report

    @Adrian - there are plenty of reasons, some technical, some administrative or political. Please don't assume that just because you can't think of valid use-cases, that there aren't any - 188 votes says otherwise.

    Personally, I use about 10-15 third-party web applications on my various sites, and this is the only one that requires me to set up a dedicated domain in order to use it.

  • Adrian commented  ·   ·  Report

    I'd give -2 to this if it was possible. Without using subdomains it's usually a huge mess to really keep things separate, and domains are extremely cheap nowadays, so there is literally no good reason to not use a subdomain of a real domain.

  • David commented  ·   ·  Report

    Please make this change available, tying to root just makes no sense.

  • Mark Carpenter commented  ·   ·  Report

    This would be a well-appreciated feature, currently we use Gitlab, Redmine, and Mattermost, It is a bear managing all 3 of them from the same server, currently, we have users just hitting the mattermost port on our internal VM, it works but it is not elegant.

  • Anonymous commented  ·   ·  Report

    I am waitting for this awesome feature and I hope it come true the sooner the better!

  • Nancy commented  ·   ·  Report

    Critical feature for me, can't install mattermost otherwise! (as part of gitlab omnibus, now I can install gitlab thanks to new relative url support in gitlab 8.5, but cannot install mattermost as part of the omnibus)

  • Ace commented  ·   ·  Report

    It would be awesome !

    Especially for self-hosted solution without a domain name (but still with a public ip)
    And others like let's chat doesn't support it either, so that would be a significant distinction

  • Carl Jahn commented  ·   ·  Report

    agree this would be really awesome

  • Fynn commented  ·   ·  Report

    I totally agree, much cleaner.

General: Mattermost Team Edition

Categories

Feedback and Knowledge Base

(thinking…)