mozilla / mattermost-heroku

Run mattermost on Heroku with an Nginx reverse proxy

Deploy Mattermost Team or Enterprise Edition to Heroku

This buildpack is an inline buildpack (tldr: this repo deploys to Heroku and uses itself as a buildpack) for deploying Mattermost to Heroku. It must be used in tandem with This customized Nginx Buildpack that allow mattermost to communicate with Nginx using a TCP port instead of a socket.

Known to work with Mattermost 4.5.0 Team and Enterprise editions

Configuration options

Buildpack Specific Variables

Set MATTERMOST_VERSION to the release version you'd like to install. i.e. '4.5.0' Set MATTERMOST_TYPE to either 'team' or 'enterprise'

Mattermost Configuration

Mattermost-Heroku supports every configuration option available in Mattermost (although some make no sense to use with Mattermost+Nginx on Heroku, i.e. "Forward80To443"). To set an environment variable, prefix it with "MM_" followed by the setting type, and then the setting key, in all upper case. You can read up about how this works in the Mattermost configuration documentation

Rebuilding

If you maintain a fork of this repo, you can link the Heroku app to your fork, which will enable you to build from the Heroku dashboard's deploy page.

An alternative to this would be to use the Heroku Build API to create a new build

For example, a curl request like this would do the trick (substitute the right variables):

curl -n -X POST https://api.heroku.com/apps/$YOUR_APP/builds \
-d '{"source_blob": {"url":"https://github.com/mozilla/mattermost-heroku/archive/{$LATEST_BUILDPACK_VERSION}.tar.gz", "version": "${COMMIT_HASH}"}}' \
-H 'Accept: application/vnd.heroku+json; version=3' \
-H "Content-Type: application/json"

The "version" parameter is optional in the example above.

This curl request can be made manually from a developer's machine, or it can be set up as a job in something like Jenkinshttps://jenkins.io/. Keep in mind that Authorization headers will need to be included in the request.

Also, the example above assumes that the machine it's being run on has heroku.com credentials saved in your ~/.netrc file.

Warnings

1. Don't make configuration changes in the Mattermost admin console. Any configuration changes in the Mattermost admin console will be lost on dyno restart (which may be every 24 hours) and will not be distributed across multiple dynos.
2. Not using s3 means any uploads will be lost on dyno restart or application reconfiguration or redeploy and won't be consistent across multiple dynos. Without s3 backing this is not anything more than a one time demo.

Enterprise Edition

Activate it as instructed in the docs https://docs.mattermost.com/install/ee-install.html

mattermost-heroku's Issues

How to get started ?

I have a MatterMost instance running on Heroku. What do I do next? I searched for a while on Google but could not find anything about what to do after you have an instance running on Heroku. Thank you in advance, Dan

Reconfigure, redeploy

Hi, Awesome buildpack.

I'm a bit puzzled with regards to reconfiguring redeploying this when using the one click deploy and the documentation states "Rebuilding - Use the deploy menu on the Heroku dashboard to trigger manual deploys." Unfortunately I don't think this is possible. Please correct me if I'm wrong but it looks to me as if the only way to trigger a Heroku deploy is via git push.

And so the way then to rebuild is (I think), do:

heroku git:clone --app YOURAPPNAME && cd YOURAPPNAME
git remote add origin https://github.com/mozilla/mattermost-heroku
git pull origin master
git push heroku master

If You find this to be correct, perhaps include it in the README.MD?

No Email Signup

Hi, I've deployed Mattermost 4.1.0 on Heroku and I've filled MM_SQLSETTINGS_DATASOURCE with DATABASE_URL.

Mattermost starts but whe I try to register first user it show this error: User sign-up with email is disabled.

The MM_EMAILSETTINGS_ENABLESIGNUPWITHEMAIL config var is true.

Why?

thanks

Build Error

Tried to deploy 5.7.1 and 5.7.0 using default or standard config settings and I'm getting:

-----> nginx-buildpack app detected

cp: cannot stat 'bin/nginx-heroku-18': No such file or directory

 !     Push rejected, failed to compile nginx-buildpack app.

 !     Push failed

Deploy to Heroku broken

with the commit to "add nginx-heroku-16"

I get this when I try to run the deploy to heroku page at https://dashboard.heroku.com/new?button-url=https%3A%2F%2Fchrisdecairos.ca%2Fdeploying-mattermost-to-heroku%2F&template=https%3A%2F%2Fgithub.com%2Fmozilla%2Fmattermost-heroku%2Ftree%2F1.0.3

-----> nginx-buildpack app detected
cp: cannot stat 'bin/nginx-heroku-16': No such file or directory
 !     Push rejected, failed to compile nginx-buildpack app.
 !     Push failed

anything I can do to fix?

Support a build number, and a build hash

Currently, Mattermoz (which is deploying using this buildpack) shows "dev" as the build number and no build hash.

These values must be generated during the Go build process. I'd like to have the build number be configurable, and the build hash available.

app.json's project is not a valid Heroku application

Build app

There was an issue building your app. This can mean your app.json's project is not a valid Heroku application. Please ensure your app is deployable to Heroku and try again.

-----> nginx-buildpack app detected
cp: cannot stat 'bin/nginx-heroku-18': No such file or directory
 !     Push rejected, failed to compile nginx-buildpack app.
 !     Push failed

Verify build hash if defined

Mattermost now includes hashes of their binaries, so the installer should verify the integrity of the download.

The SHA can be optionally provided via an environment variable.

Wiki changes

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• the wiki has been disabled, as it was not used

These were made as the result of a recent automated defacement of publically writeable wikis.

Update buildpack for 3.7.0

• check compatibility
• Add new ENV vars
• update default version
• update README

Custom Repo

When I deploy my custom repo of mattermost through this buildpack, the instance keeps on crashing. I am using git clone to clone my compiled version of mattermost to the instance, but the instance crashes after deployment. Is there a better way to deploy a custom repository on Github to heroku?