No description
This repository has been archived on 2024-11-03. You can view files and clone it, but you cannot make any changes to it's state, such as pushing and creating new issues, pull requests or comments.
Find a file
Hanzei b303e8da00 Add make help target (#19)
* Add make help target

* Move documentation to previous line
2018-11-08 16:30:58 -05:00
build Update Mattermost to v5.4 2018-10-17 07:19:22 +02:00
server Update Mattermost to v5.4 2018-10-17 07:19:22 +02:00
webapp fix index.js import of plugin id 2018-09-20 14:21:10 -04:00
.gitignore initial commit 2018-07-23 13:43:22 -04:00
.travis.yml Add make check-style to travis 2018-10-12 14:56:57 +02:00
CHANGELOG.md initial commit 2018-07-23 13:43:22 -04:00
LICENSE initial commit 2018-07-23 13:43:22 -04:00
Makefile Add make help target (#19) 2018-11-08 16:30:58 -05:00
plugin.json strip out sample bits (moved to demo repository) 2018-07-24 16:02:46 -04:00
README.md add travis badge (#20) 2018-11-08 13:12:13 -05:00

Sample Plugin Build Status

This plugin serves as a starting point for writing a Mattermost plugin. Feel free to base your own plugin off this repository.

Getting Started

Shallow clone the repository to a directory matching your plugin name:

git clone --depth 1 https://github.com/mattermost/mattermost-plugin-sample com.example.my-plugin

Edit plugin.json with your id, name, and description:

{
    "id": "com.example.my-plugin",
    "name": "My Plugin",
    "description": "A plugin to enhance Mattermost."
}

Build your plugin:

make

This will produce a single plugin file (with support for multiple architectures) for upload to your Mattermost server:

dist/com.example.my-plugin.tar.gz

There is a build target to automate deploying and enabling the plugin to your server, but it requires configuration and http to be installed:

export MM_SERVICESETTINGS_SITEURL=http://localhost:8065
export MM_ADMIN_USERNAME=admin
export MM_ADMIN_PASSWORD=password
make deploy

Alternatively, if you are running your mattermost-server out of a sibling directory by the same name, use the deploy target alone to unpack the files into the right directory. You will need to restart your server and manually enable your plugin.

In production, deploy and upload your plugin via the System Console.

Q&A

How do I make a server-only or web app-only plugin?

Simply delete the server or webapp folders and remove the corresponding sections from plugin.json. The build scripts will skip the missing portions automatically.