jarvis-bot
Advanced tools
A JARVIS for your team - your most powerful bot and loyal butler. Jarvis was originally built for GLOBAL_HACKERS as our smart, humorous and sentient team assistant.
The most popular and powerful features for us include todo, reminder, memes, search, and a machine learning module. See the design and all the features.
Clone this git repo:
git clone <the-url-of-this-repo>
Also available as an NPM package:
npm install jarvis-bot
Next, install the dependencies:
npm install
Tl;dr: If you're using Slack, just set bin/.env file, fill the bin/.env-jarvis with API tokens and run npm start.
npm start runs app.js, which uses forever-monitor. This is for when you don't have sudo to install forever on the machine you're deploying on. This has the issue of nested processes not being terminated properly (a forever issue.)
Things are nicer if you use forever from the terminal, you can deploy/stop multiple instances (after specifying the right file in .env) like below:
forever start --killSignal=SIGTERM -a -l jarvis.log --uid "jarvis" run.js
forever start --killSignal=SIGTERM -a -l veronica.log --uid "veronica" run.js
Note that you must set --killSignal=SIGTERM to properly kill off hubot. You can kill like below:
# stop an instance
forever stop jarvis
# stop all instances
forever stopall
I'm a lazy person. So I save the forever commands above in the npm scripts. For example in package.json:
"scripts": {
"start": "node app.js",
"stop": "forever stopall",
"jarvis": "forever start --minUptime=1000 --spinSleepTime=1000 --killSignal=SIGTERM -a -l jarvis.log --uid 'jarvis' app.js",
"veronica": ...
},
So instead of typing that long command for forever, you can
# runs that long forever command
npm run jarvis
To stop all forever processes,
npm stop
Jarvis uses many APIs, and some of them need tokens. Set the environment variables for each instance of your bot in bin/.env-<bot>. Most of them should be straightforward to obtain, others you can Google how to. Below is a few, explained:
HUBOT_SLACK_TOKEN: You have to add a bot integration under your Slack team setting, and generate a token to use.HUBOT_REPOPATH: This is the bot's repo that you're syncing the memory with.HUBOT_GHTOKEN: To sync memory (upload to Github), you need to allow access and generate a token from your account.HUBOT_GOOGLE_API_KEY: You need a Google developer account, then create a project, choose the APIs to enable, and generate a "browser token" from the Google Developer Console.Beware, don't expose your .env-<bot> files to other people. That's common sense.
A few bot functions such as memory upload and twitter posts are restricted to admins. Specify their email addresses, comma separated, in bin/.env-<bot>. Note that the incoming user object from Slack has the email field, so if you're using a different adapter, you may need to hack around it from scripts/helper.coffee.
The reason for using email address is because username can be changed (in Slack) and thus be faked.
The default adapter is Slack. To change it, find them here. NPM uninstall hubot-slack, install your adapter, and specify it in bin/.env.
Since the text formatting are meant for Slack, you may need to hack the scripts a bit when you're using a different chat platform, especially with how the admin emails are recognized.
If you're using Slack, then deployment is super simple. Simply set your API keys in bin/.env-<bot> and specify which bot to deploy in bin/.env, then you're ready. See Setup.
Deploy anywhere you want: Heroku, GCloud, AWS, your local Unix machines. There is no need to setup the bot environment variables yourself because app.js handles them for you. As long as npm install and npm start (which runs node app.js) are run, you're good.
Jarvis is quasi-immortal. He will never sleep (uses cron), and will resurrect upon death (uses forever-monitor).
Test-run locally with
npm start
Even though Jarvis is platform neutral, we deploy ours to Google Cloud, so the files .dockerignore, Dockerfile, app.yaml are needed. Remove and add any deployment config files as you need if you deploy somewhere else.
We built Jarvis to be the smart assistant for our team. The design is based on hubot, and we have made significant improvements to its core but you probably won't notice. So, if you've had experience with hubot, you'll know how to extend Jarvis by writing your own scripts.
Jarvis' internal modules are different from the original hubot:
hubot-keep-alive is removed and replaced by the more elegant cronscripts/cmdhelp.coffeeAll the modules and hubot scripts are in node_modules and scripts, following the original hubot design. lib contains your non-hubot-interface scripts. In short, organize as you like, but the bot interface scripts shall be in the scripts folder.
Just like the original hubot, Jarvis is platform-neutral. We deploy our Jarvis on Slack, but you can choose your own platform by simply changing the adapter (see Setup).
The powerful thing is that you can access Jarvis from anywhere! We use Slack, so we can call Jarvis from the Slack apps for mobile, laptop, and web.
We lost count on the number of features. There's currently over 30 modular scripts (some under node_modules). Feel free to remove/add any from your bot as you like. If you got a brilliant idea, suggest to us!
You don't have to do much to start using Jarvis. Just get your API keys/tokens for the APIs you wish to use to put in .env-jarvis under bin/. If you have several teams to deploy the bots for, you can have multiple .env-<bot> files. Before deploying, specify the bot you wish to deploy in .env.
This assumes you're using Slack of course. For more advanced tweaks, see Setup.
Jarvis is designed to be deployed anywhere. All its internal environment variables are specified in .env-<bot> file, and it sets them automatically when run. This nicely prevents fragmentation of providing different env files per deployment, like app.yaml for Gcloud, and app.json for Heroku.
We use Slack, but you can just use pretty much anything else: Whatsapp, Telegram, FB chat, Skype. Just replace the hubot adapter by specifying it in package.json and .env.
The powerful thing is that you can access Jarvis from anywhere! We use Slack, so we can call Jarvis from the Slack apps for mobile, laptop, and web.
My team likes to break things, and Jarvis was the obvious target.
Jarvis is quasi-immortal. He will never sleep (uses cron), and will resurrect upon death (uses forever-monitor). So, kill him as many times as you wish, he will always come back to live, unless if the server farm gets nuked of course.
There are things that should be accessible only to admins. One example is memory sync (below), where only admins can make Jarvis upload his memory. See .env-<bot> to set the admins for each bot.
We constantly improve Jarvis, thus the source code is kept on Github. However, when we redeploy Jarvis (due to death or new iteration), we want him to remember us.
Jarvis's hubot.brain.data persistent memory is kept under memory/braindata.json. You can get creative and make your own modular memory.
When deployed, Jarvis can sync its new memory with its Github, so before redeploying, you can just do git pull to update the local memory. Then the new Jarvis will remember.
It's scheduled to auto-upload its brain to Github every midnight, but admin can also manually tell Jarvis to do so. The commands for this module is hidden to prevent tampering, so dig into the source code. See scripts/memsync.coffee, where you can set a magic word to call, and if you're an admin, Jarvis will upload his brain.
You can organize all your help commands into types. See typedCmd in scripts/helper.coffee, where the JSON goes from type to module to the command regex of the module. Currently there are 3 types: fun, bot, util, and each has its own modules(named as you like). The array for each module contains its command regexs, which are used for preventing conflict in input-parsing.
Below is the help in action, going down the level of specificity. Furthermore, help <term> displays all the helps that match the <term>.
Jarvis recognizes users by their usernames; you can also add aliases.
With the recognition, Jarvis can serialize its functions such as weather and reminders to cater to individual users. You can call the functions using aliases too. Furthermore, Jarvis will recognize fuzzy usernames (lexicographically, so be careful).
Our team is global, so it's handy to know where someone is and the time there. User serialization is used here, so simply tell Jarvis where you are, and when you call the functions, Jarvis will use your location.
Jarvis can remind you of things at certain time, and keep a todo list for you. Of course you can have Jarvis remind your teammates of their tasks.
Reminder is time sensitive, and defaults to 1h if time is not specified:
Todo list is not time sensitive:
Jarvis uses many Google APIs (you'll need your own Google developer API keys) to use them.
Jarvis recognizes me or user aliases when using locations.
No hackers can do without Hackers News, so here it is:
Jarvis can search on Twitter, and post (admin only).
This is the first stage of an AI Jarvis, and scripts/sentiment.coffee is its first machine learning module. This pulls search results from Twitter, feeds it to Indico.io, and returns the sentiment. This is especially handy for observing the trend of a topic on Twitter, say a stock.
Expect more AI/ML features to come soon, since the author is studying that.
Lomath is a math library extended from lodash. You can evaluate a lomath function from Jarvis as you would code it, which also means you can use lodash.
To make Jarvis more human-like, we added a chatbot module to it. Whenever you say something that doesn't match a command regex of typedCmd in scripts/helper.coffee, it will be redirected to the chat module.
The chat module is serialized for each user, so Jarvis can keep the conversations separate. Here's our best picks:
Jarvis gone sentient:
Jarvis gone sentient, confirmed:
This is easily the most-used feature. Warning: this may cause dramatic swings in productivity, use with caution! Currently includes: meme generator, coding love, cat, pug, chuck norris, Shia Labeouf, Donald Trump, flirt, etc.
Sep 2
forever commands from npmAug 25
Aug 8
FAQs
A JARVIS for your team - your most powerful bot and loyal butler.
We found that jarvis-bot demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.