view release on metacpan or  search on metacpan

examples/dashboard/README.md  view on Meta::CPAN

## Dashboard

> *Try a [live demo](https://beekeeper.net.ar/dashboard/) of this dashboard*

![](../../doc/images/dashboard.png)

To use the dashboard start the worker pool:
```
cd beekeper/examples/dashboard
source setup.sh
./run.sh
```
Then open `dashboard.html` in a browser. 

Logs can be inspected with `bkpr-log` or with:
```
tail /var/log/myapp-pool.log
tail /var/log/myapp-service-dashboard.log
```
Finally stop the worker pool with:
```
./run.sh stop
```
---

### Dashboard users setup

Dashboard users must be declared into config file `dashboard.config.json`:

```
{
    "users": {
        "admin": { "password": "eea8d7042107a675..." },
        "guest": { "password": "60c8d0904b5deb4c..." },
    },
}
```
You will need to reset passwords before being able to login into the dashboard.  
Use the following command to hash passwords of dashboard users:

```
echo "Username:" && read U && echo "Password:" && read -s P && echo -n "Dashboard$U$P" | shasum -a 256 && U= P=
```
---

### Mosquitto setup

This dashboard uses WebSockets, so it cannot be run with ToyBroker: a real broker like
[Mosquitto](https://mosquitto.org/) is required. Follow the instructions below to quickly 
setup a Mosquitto instance capable of running Beekeper applications with minimal security. 

Please note that the entire idea is to have the backend and frontend buses serviced by different
broker instances, running on isolated servers. This setup uses a single broker instance for 
simplicity, and works  just because topics do not clash (see [Brokers.md](../../doc/Brokers.md) 
for a proper configuration).

Create `/etc/mosquitto/examples.conf`
```
per_listener_settings   true
max_queued_messages     10000
set_tcp_nodelay         true

## Backend

listener            1883  127.0.0.1