The Nestor Power Development Toolkit lets you create, test and deploy Nestor Bot Powers.
A Bot Power is functionality that you would like to add to Nestor. Examples of powers include Github and Trello. But what if you wanted to add your own?
Nestor Power Development Toolkit comes to the rescue.
Download the Nestor CLI tool . Downloads are available for OS X and Linux. (Windows coming soon).
Unpackage the archive and move the nestor binary to a well-known $PATH (such as /usr/local/bin).
To start creating your own power, run nestor new . So if you wanted to call your power "Hello World", run this command:
$ nestor new "Hello World"
Quotes are not needed if the name of your power is a single word.
This will create a NodeJS module with the following contents:
index.js: Contains a sample power implementationpackage.json: Where you can add all your dependencies. The nestorbot dependency is added by default.
nestor.json: A manifest file containing details about your powerREADME.md: Contains the Nestor programming manual
You can now follow the Nestor Programming Manual to make changes to your power.
The nestor.json file located at the root of your power's directory contains important information that is required by Nestor:
name: The name of your powerpermalink: The permalink that will uniquely identify your power. The permalink must not contain any spaces.Description: A short description of what users can do with this power.These three fields are mandatory.
In addition if your power requires environment variables that need to be configured (for e.g. authentication tokens or keys), you can set them with the environment_keys fields.
An example of this setting can be found in the Mixpanel power
json
"environment_keys": {
"NESTOR_MIXPANEL_API_KEY": {
"required": true,
"mode": "user"
},
"NESTOR_MIXPANEL_API_SECRET": {
"required": true,
"mode": "user"
}
}
In this example, NESTOR_MIXPANEL_API_KEY and NESTOR_MIXPANEL_API_SECRET are both required (specified by "required":true) by the power to work and need to be set by the user (specified by "mode": "user")
By setting an environment variable to be "required", every time a user tries to use your power, she will be prompted to set this environment variable. This way you don't have to write additional code in your power to check whether your environment variable is set.
If you have an optional environment variable, then set the required field to false.
An example of an environment variable that is not required can be found in the Github power.
To save your Nestor power, run nestor save inside the directory where you power is created and this will upload the code powering your power (pardon the pun) to Nestor's servers and your power is now ready to be tested.
$ nestor save
Saving your power does not make it available to your Slack team. You will still need to deploy your power (which we will cover later in this README).
All of the remaining operations (including this one) require you to be authenticated with Nestor's service so you will be prompted to log in. If you are logging in for the first time, you will need to sign in to the website, go to "My Profile" by clicking on your profile picture on the left bottom side, and setting your password.
Keep note of your email address as that is required to log in.
The Nestor Toolkit provides you with an interactive shell which will let you test your power before it is deployed. You can enter text commands as they would appear in Slack, and see how your power behaves.
You can keep editing your power, save-ing your changes and keep testing it with the shell until you are happy.
To start the shell, run the following command:
$ nestor shell
To quit the shell, enter the command exit.
Deploying your power means that your power will now be available to your entire team. To deploy your power run the following command:
$ nestor deploy
This will give you a list of versions for your power (every time you save your power, a new version is created) and you can pick the version that you want to deploy.
If you want to deploy just the latest version, run:
$ nestor deploy --latest
To report bugs and make feature requests, please create an issue.