muesli/beehive is one of the automation-focused repositories TopGit tracks, currently at 6.5k stars, written primarily in Go. A flexible event/agent & automation system with lots of bees 🐝
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Beehive is an event and agent system, which allows you to create your own
agents that perform automated tasks triggered by events and filters. It is
modular, flexible and really easy to extend for anyone. It has modules
(we call them Hives), so it can interface with, talk to, or retrieve
information from Twitter, Tumblr, Email, IRC, Jabber, RSS, Jenkins, Hue - to
name just a few. Check out the full list of available Hives
in our Wiki.
Connecting those modules with each other lets you create immensly useful agents.
Here are just a few examples of things Beehive could do for you:
Re-post tweets on your Tumblr blog
Forward incoming chat messages to your email account
Turn on the heating system if the temperature drops below a certain value
Run your own IRC bot that lets you trigger builds on a Jenkins CI
Control your Hue lighting system
Notify you when a stock's price drops below a certain value
Installation
Packages & Binaries
Arch Linux: beehive (AUR)
Linux Static 64bit
Linux Static armv6
macOS 64bit
Windows 64bit
You can find even more official releases here.
Deployment Tools
Docker: docker run --name beehive -d -p 8181:8181 fribbledom/beehive
Ansible
From source
Beehive requires Go 1.13 or higher. Make sure you have a working Go environment.
See the install instructions.
The recommended way is to fetch the sources and run make.
git clone --recursive https://github.com/muesli/beehive.git
cd beehive
make
You can build and install the beehive binary like other Go binaries out there (go get)
but you'll need to make sure Beehive can find the assets (images, javascript, css, etc).
See the Troubleshooting/Notes section for additional details.
Run beehive --help to see a full list of options.
Configuration
Think of Hives as little plugins, extending Beehive's abilities with events you
can react on and actions you can execute.
Just as examples, there's a Twitter plugin that can
react to someone you follow posting a tweet (an event)
post a new tweet for you (an action)
...
or an RSS plugin that lets you
monitor RSS feeds and react on new feed items (another event)
or an email plugin that gives you the ability to
send emails (another action)
Each Hive lets you spawn one or multiple Bees in it, all working independently
from another. That allows you to create separate plugin instances, e.g. one
email-Bee for your private mail account, and another one for your work email.
Creating Bees
Sounds complicated? It's not! Just for fun, let's setup Beehive to send us an
email whenever an RSS feed gets updated. Start beehive and open http://localhost:8181/
in your browser. Note that Beehive will create a config file beehive.conf
in its current working directory, unless you specify a different file with the
-config option.
Note: If you built Beehive with go build instead of make you will have to
start beehive from within its source directory in order for it to find all the
resources for the admin interface. Also see the Troubleshooting & Notes section
of this README.
The admin interface will present you with a list of available Hives. We will
need to create two Bees here, one for the RSS feed and one for your email
account.
Setting up a Chain
Now we will have to create a new Chain, which will wire up the two Bees we just
created. First we pick the Bee & Event we want to react on, then we pick the
Bee we want to execute an Action with. The RSS-Bee's event gives us a whole set
of parameters we can work with: the feed item's title, its links and
description among others. You can manipulate and combine these parameters with
a full templating language at your disposal. For example we can set the email's
content to something like:
Title: {{.title}} - Link: {{index .links 0}}
Whenever this action gets executed, Beehive will replace {{.title}} with
the RSS event's title parameter, which is the title of the feed item it
retrieved. In the same manner {{index .links 0}} becomes the first URL of
this event's links array.
That's it. Whenever the RSS-feed gets updated, Beehive will now send you an
email! It's really easy to make various Bees work together seamlessly and do
clever things for you. Try it yourself!
You can find more information on how to configure Beehive and examples
in our Wiki.
Troubleshooting & Notes
The web interface and other resources are embedded in the binary by default.
When using make noembed, Beehive tries to find those files
in its current working directory, so it's currently recommended to start Beehive
from within its git repository, if you plan to use the web interface.
Should you still not be able to reach the web interface, check if the config
directory in the git repository is empty. If that's the case, make sure the
git submodules get initialized by running git submodule update --init.
The web interface does not require authentication yet. Beehive by default
accepts all connections from the loopback device only.
If you want to bind Beehive to a different interface/address, run Beehive with
the -bind and -canonicalurl parameters. For example:
How does muesli/beehive compare to other Automation projects?
muesli/beehive is tracked by TopGit in the Automation category, with 6.5k GitHub stars and written in Go. Browse the Automation topic page on TopGit to compare it against similar projects by stars and activity.
Is muesli/beehive open source?
Yes — muesli/beehive ships under the AGPL-3.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/muesli/beehive.
What else is in the Automation space?
muesli/beehive is tracked by TopGit under the Automation category, alongside 5 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is muesli/beehive?
muesli/beehive (muesli/beehive) is a Go project on GitHub. From the project's own README: A flexible event/agent & automation system with lots of bees 🐝
Where do I read more about muesli/beehive?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/muesli/beehive is the definitive source.
Why is muesli/beehive categorized under Automation?
TopGit places muesli/beehive in the Automation category based on its GitHub topics and description (tagged: "automation", "event-driven", "hacktoberfest"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Still deciding about beehive?
One click hands the question to an AI along with this page — see what it says about beehive.