codersontheroad / lighthouse-dashboard Goto Github PK

:speedboat: This is a monitoring dashboard for rescue teams receiving distress alerts from the refugees at sea using the Lighthouse mobile app.

Home Page: http://codersontheroad.org/lighthouse-app/

JavaScript 66.29% HTML 21.31% CSS 12.39%

lighthouse-dashboard's Introduction

Lighthouse Dashboard

This is a dashboard for alerts sent using the Lighthouse application.

How to build

In order to build this project you need to have NodeJS, npm and Bower installed on your computer.

Install all npm modules : npm install
Install all bower components : bower install

Install Compass

It may be necessary to do a global and local installation for the project's Compass CSS/Sass framework to work:

Global install: npm install -g compass
Local install (inside the project directory: gem install compass

How to run

This project is currently configured to run with the default web server offered by grunt :

grunt serve

To access the dashboard section of the app

Go to: http://localhost:9000/#/dashboard

lighthouse-dashboard's People

Contributors

Stargazers

Watchers

Forkers

daneasterman

lighthouse-dashboard's Issues

Fix filter button

It seems the filter button does not perform any particulat action

"Warning: Not Found: Compass"

Hi guys, I keep getting this error message when running grunt serve:

Running concurrent:server (concurrent) task
Warning: Running compass:server (compass) task
Warning: not found: compass Use --force to continue.
Aborted due to warnings.
Execution Time (2016-03-26 13:14:46 UTC)
loading tasks 144ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 68%
loading grunt-contrib-compass 60ms ▇▇▇▇▇▇▇▇▇ 28%
compass:server 8ms ▇▇ 4%
Total 213ms Use --force to continue.
Aborted due to warnings.

Then when using --force (which I read after shouldn't be done), there are of course no styles.

I've tried a few things based on Stack Overflow advice:

gem install compass (says needs ruby gemfile for compass to work)
Did separate global installs with npm: npm install -g grunt-contrib-compass
npm install -g compass
Ran RubyGems update gem update --system

But nothing has worked so have run out of ideas now. Thanks a lot for the help in advance!

Daniel

Repair remove button

The remove button seems to be unresponding some times.

Eg. 2 alerts received, one acknowledged, the second one cannot be removed.

Investigate whether there is a mechanism hindering the removal of acknowledged alerts on purpose

Add device ID to retrieve their status/acknowledgement

Retrieving the device ID performing the alert can help retrieve its status if connection is lost or page/app closed/reopened.

Will also prevent spamming

Change color on marker when hovering table row entry

Add a focus on the marker corresponding to the entry being hovered on in the table.

Warnings when running npm install

When I run

npm install

I get the following warnings:

peerDependencies The peer dependency jasmine-core@* included from karma-jasmine will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma@>=0.9 included from karma-phantomjs-launcher will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency phantomjs-prebuilt@>=1.9 included from karma-phantomjs-launcher will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma@^0.13.0 || >= 0.14.0-rc.0 included from grunt-karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN deprecated [email protected]: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0
npm WARN deprecated [email protected]: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0
||

Fix coordinates map focus

Seems like the coordinates focus of the map jumps from Schaerbeek to Cambridge to London