That's it! Now when you start Rocket.Chat with the meteor command, it will use your local Apps-Engine instead of the one on NPM :) Where PATH_TO_APPS_ENGINE is the path to the Apps-Engine repo you've cloned. When developing new functionalities, you need to integrate the local version of the Apps-Engine with your local version of Rocket.Chat.įirst of all, make sure you've installed all required packages and compiled the changes you've made to the Apps-Engine, since that is what Rocket.Chat will execute: Some features the Engine allows Apps to use: Send messages to users and livechat visitors.The Apps-Engine is Rocket.Chat's plugin framework - it provides the APIs for Rocket.Chat Apps to interact with the host system. What does the Apps-Engine enable you to do? Simple interface with settings and checkbox to allow/disallow them. Idea is to allow the implementer to have a default set of restricted ones while letting the admin/owner of the server to restrict it even further or lift the restriction on some more.

The implementer of this should restrict the server setting access and environmental variables.The language strings are only done on the clients ( TAPi18next.addResourceBundle(lang, projectName, translations) ).Apps which don't provide a valid uuid4 id will be assigned one, but this is not recommended and your App should provide an id.

Rocketchat client