Skip to content
Go to file


Failed to load latest commit information.
Latest commit message
Commit time

BEEP - Open source bee monitoring (v2.2.1)

BEEP is a combination of a bee monitoring (Laravel PHP) framework API + an (Angular JS) app and a (Influx) time series sensor data database. There are also first steps of creating cost efficient measurement hardware.

It's key feature is to integrate a user friendly responsive app for manual inspections with automatically measured sensor data.

Create a login and check the live app at:

System overview

BEEP System overview

You are free to use the BEEP app, it's free and it will be developed further in the near future. If you would like to install it on your own server, or contribute; please read on below.

Installation of API and APP (on your own server)

0. Server specs

NB: You can use this gist to install all the software you need: LAMP PHP 7.2

1. Clone this repo anywhere you like

git clone

2. Database

Create a MySQL database (type: InnoDB, encoding: UTF_8, collation: utf8_unicode_ci) called:


NB: Make sure to pass the user and credentials to the newly made .env file after step 3.

3. Install required vendor libraries

a. Make the file executable by chmod +x This bash script will install all the packages and vendor dependencies that you need at once.

b. Then run it: ./

NB: To stick to a certain PHP version (on the server e.g. 7.1.25), use composer install --ignore-platform-reqs or composer update --ignore-platform-reqs

4. Set up your end-points

a. Make sure your server has 2 different virtual hosts for the API and the APP

NB: On Amazon AWS (Bitnami LAMP_7.1): a. Make sure your Bitnami server includes your apps/apache_vhost.conf in

sudo nano /opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf

Contains one or more Includes:

# Bitnami applications installed in a Virtual Host
Include "/opt/bitnami/apps/apache/portal-vhost.conf"

Bitnami restart apache server:

sudo /opt/bitnami/ restart apache

API (replace '' with your own server/test domain)

    DocumentRoot /var/www/bee/public
    ServerName ""

    <Directory /var/www/bee/public/>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride All
        Order allow,deny
        allow from all


APP (replace '' with your own server)

    DocumentRoot /var/www/bee/public/webapp
    ServerName ""

    <Directory /var/www/bee/public/webapp/>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride All
        Order allow,deny
        allow from all


b. Optionally, install SSL certificates to your endpoints with Let's Encrypt


sudo /opt/bitnami/letsencrypt/scripts/ -m -d -d

On other servers with command: sudo certbot --authenticator webroot --installer apache

5. Add Influx database

> exit

NB: Make sure to pass the user and credentials to the .env file that has been created in step 3. NB: If your Influx version was < 1.1.x (no TSI support), when using backups to transfer data: first install the old version that you are currently using on a new server, import the backups, then update to the newest Influx version!

6. If you would like to easily deploy your fork (or this repo),

a. Make sure to add your repo to git remote: git remote set url

b. Run ./ to update your clone on any server

Configuring the back-end system

1. Check database tables

If you did not run ./run_actions, please do so, to install all the database tables and set up the default categorization.

2. Set up valid credentials

a. Set up e-mail credentials in the .env config file

b. For the webapp to reach the API, rename the file 'public/webapp/js/constants.js.example' to 'public/webapp/js/constants.js' and edit it to change the 'api_url' to your own back-end API end-point

c. To enable schedules (e.g. for loading weather data), install a crontab with sudo crontab -e and add: * * * * * cd /home/bitnami/apps/appdir && /opt/bitnami/php/bin/php artisan schedule:run >> /dev/null 2>&1

3. Register new user

a. Go to api.[your_domain]/webapp#!/login/create

b. Create a new user

c. Promote the user to 'superadmin'

Open your database (with a database viewer like PhpMyadmin, Sequel Pro, MySQL Workbench, etc.), or just do a command line query: Define a relation in table role_user with (1,1) (linking user_id 1 to role_id 1).

Your user has just been promoted to the super administrator of the system, so you can use the back-end management interface to configure the complete system.

d. Go to api.[your_domain]/admin to log in with the same credentials that you created your app user with in step 3b.

e. You should see the back-end dashboard, looking like this:

Management interface

BEEP Management interface

Installation using docker compose

A simple setup for small installations can be achived with docker-compose. The tool will spinn up a mysqldb, influd, a webserver and initialize the beep database.

  1. Install docker-compose
  2. Checkout BEEP and switch into the code repository
  3. Adjust docker-compose.yaml(set suitable environment variables).
  4. Run docker-compose up. During the first start, you might see some database connectivity issues. Docker compose will restart the BEEP Server component untill a database connection is available. So don't worry.
  5. Register as a new user: http://localhost:8000/webapp.
  6. Grant user administrator rights: docker-compose exec mysql mysql -h localhost -P 3306 -ppass -u user -D bee_data -Bse "INSERT INTO role_user (user_id,role_id) VALUES(1,1);"
  7. Login to mamagement interface: http://localhost:8000/admin

To upgrade beep to the latest version, simply stop and start docker-compose.

As the setup is based on docker containers, code changes inside the repository will not have an effeact till the underlying docker image is updated.

Get your BEEP base measurement data into the BEEP app

  1. Create a TTN account at (or other LoRa network) and create an HTTP integration pointing to, or point your own measurement device data stream HTTP POST to (please refer to our Slack channel for API description)
  2. Use the native Android / iOS app to configure your BEEP base by Bluetooth.
  3. With the app, connect the BEEP base to the BEEP TTN network (auto configuration), or connect the BEEP base (manually) to your own LoRa network
  4. The native app adds a BEEP base measurement device to your BEEP account
  5. You can see the measurement data at the Measurements menu item of the webapp


Thank you for considering contributing to the BEEP framework! If you would like to contribute, please fork this repository, edit on your Github account, and finally send Pull Requests to this repository to include new features.

Adding a language

  1. Create a Beep user account at!/login/create
  2. Fork this repo
  3. Send an e-mail to with you user e-mail address, asking to become a translator for a certain language
  4. Log into the backend to start translating


Please request access to if you would like to see the roadmap and cooperate.

In short on our roadmap:


  • Many new features for health checking and sensor (2019 Q3 - 2023 Q3)


  • App v3 - January 2020
    • Photo addition
    • Weather data
    • Research
    • Helpdesk integration
  • BEEP base v3 (2019 Q3-Q4)
  • App v2.1.0 - May 29 2019
    • Collaborate: Hive, data and inspection list sharing (2019 Q2)
    • User feedback improvements (2019 Q1 + Q2)
  • App v2.0.2 - April 30 2019
    • Integration sensor data / hive inspections (2018 Q4)
  • BEEP base v2 - December 2019
  • App v2.0 - July 10th 2018
    • Apiary and hive overview improved
    • Dynamic inspection list
    • Create your own inspection list and order
    • Automatic measurement view improvement
  • App v1.0 - June 15th 2017
    • One click creation of apiaries with multiple hives
    • Manual hive inspections
    • Display automatic measurements


Documentation and manual of the app can be found at

Security Vulnerabilities

If you discover a security vulnerability within BEEP, please send an e-mail to


The BEEP framework is open-sourced software licensed under the GNU AGPLv3 license.

You can’t perform that action at this time.