Currently, there is a make sync command that is supposed to help keep plugins updated with the starter template, to benefit from latest improvements&updates done to the starter.
Sadly, it is not featured in the GH repository's README, nor easy of use (it fails for me, probably because I missed some pre-required steps which is part of the missing documentation).
There are also undocumented environment variables supported by the Makefile (like MM_DEBUG, MM_SERVICESETTINGS_ENABLEDEVELOPER...) that would be worth mentioning in the README, explaining how and why to use them would be interesting. I assume from the name that they are also used for Mattermost development, but not all plugin developers have knowledge of Mattermost development (nor a local MM dev environment, because you can use Docker to test a plugin).
Currently, there is a
make synccommand that is supposed to help keep plugins updated with the starter template, to benefit from latest improvements&updates done to the starter.Sadly, it is not featured in the GH repository's README, nor easy of use (it fails for me, probably because I missed some pre-required steps which is part of the missing documentation).
There are also undocumented environment variables supported by the
Makefile(likeMM_DEBUG,MM_SERVICESETTINGS_ENABLEDEVELOPER...) that would be worth mentioning in the README, explaining how and why to use them would be interesting. I assume from the name that they are also used for Mattermost development, but not all plugin developers have knowledge of Mattermost development (nor a local MM dev environment, because you can use Docker to test a plugin).