tommyvn / mattermost-heroku

Run mattermost on Heroku

Mattermost + inline buildpack == Mattermost on Heroku

Warnings

1. Don't make configuration changes in the Mattermost admin console. Any configuration changes in the Mattermost admin console will likely be lost on dyno restart (which may be every 24 hours) and will likely 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.
3. This is tested up to v1.4.0. It will work beyond that so long as the config file format doesn't change.

ToDo

1. More configurable options

Thanks

1. https://github.com/dominictarr/JSON.sh.git for a json parser that's small enough to vendor in.

mattermost-heroku's Issues

Push failed: Utils::CytokineUnknownError

I'm getting the following error message when trying to push to heroku:

-----> Fetching set buildpack https://github.com/kr/heroku-buildpack-inline.git... done
-----> Mattermost app detected
-----> Retrieving mattermost tar from https://github.com/mattermost/platform/releases/download/v2.0.0/mattermost.tar.gz
-----> Discovering process types
Procfile declares types -> web
-----> Compressing...
Done: 29.1M
-----> Launching...
! Push failed: Utils::CytokineUnknownError
! Please try pushing again.
! If the problem persists, see http://help.heroku.com/and provide Request ID da31f10a-f11b-44e6-a2ba-452ac525ac08.

Verify Installer with Mattermost v2.1

Hey @tommyvn,

Just wanted to inform you of a number of config.json updates since Mattermost v1.4 and verify that the installer is still compatible with our latest release, v2.1.0. You can view the Mattermost Changelog here, that includes the following config.json compatibility updates from v1.4 > v2.1:

• Under ServiceSettings in config.json:
  • "AllowCorsFrom": "" to allow the system to serve HTTP requests to other domains specified.
  • "EnableCommands": false to set whether users can create slash commands from Account Settings > Integrations > Slash Commands
  • "EnableOnlyAdminIntegrations": true to restrict integrations to being created by admins only.
  • "EnableInsecureOutgoingConnections": false sets whether outgoing HTTPS requests can accept unverified, self-signed certificates.
  • Optional: "WebsocketSecurePort" : 443 sets the port on which the secured WebSocket will listen using the wss protocol. If this setting is not present in config.json, it defaults to 443.
  • Optional: "WebsocketPort": 80 sets the port on which the unsecured WebSocket will listen using the ws protocol. If this setting is not present in config.json, it defaults to 80.
• Under EmailSettings in config.json:
  • "EnableSignInWithEmail": true allows users to sign in using their email.
  • "EnableSignInWithUsername": false sets whether users can sign in with their username. Typically only used when email verification is disabled.

Thanks for contributing to the Mattermost community!