The logweb from pchudzik

When there is duplicated log message (same date, same text etc). It should be skipped

detect single log message

detect log message.
When single provider event contains multiple log entries then split them into multiple events.

It might be tricky because sometimes logs are not just single line text.

xml | html in log message is missing in gui

when there is xml/html in input it's not handled properly in gui

migrate backend jshint to eslint

Make it consistent with frontend.
I was unable to find jsx + jshint. So I used jshint
Now I can not disable jshint because it ill ignore backend so the easiest solution will be to change backend jshint to eslint.

Configure system events listener which will handle all system events

Not sure if #4 is required.
Maybe it should all reside in memory.
But then if everything is in the memory it will be hard to trace bugs and issues because after restart all is lost.
Maybe logging should be done to file, with default input which will handle and expose all system log messages.

log logweb information to file

log system events like provider failure etc

add bin section to package.json

install runnable application in node_modules/.bin
then you can publish to npm and install it using npm install logweb

add support for forever - https://www.npmjs.com/package/forever so process will fun forever

setup backend tests

as in title

bind message container to top of the page and animate messages

This will require to fix webpack to include css.
try to use scss with webpack

get rid of lodash in backend

Edit providers configuration from gui

create frontend
expose api
save data to file
restart input - #29

change favicon when new data arrives

When new log entry is added and user is not focused in application change favicon so user will now that new data is present.

Prepare pretty dashboard

Consider what should be included in the dashboard.
Maybe events per second/second (refresh cycle)
Last event date etc?
Total number of events (need to be implemented because otherwise it will be stuck on buffer size)

retry watch command on error

as in title. When provider command fails then restart it

use frontend framework

as in title.
Angular is simplest choice. But it might suck with big log files so maybe react will be better?

make toggle follow buttons more visible

opacity to .8 for starters.

loading indication blinks

When receiving data loading indicator blinks.
I think loading indicator should be set as footer. and log messages should have bottom-padding to make it work properly.

Add possibility to restart log input

Expose api and add frontend button which will restart input provider.

When restart is done then it should be easier to edit configuration in gui.

setup ci

setup travisci as testing environment

fixup frontend to make it usable

nothing fancy. Just make sure new events are appended to <pre> or <code>
Get rid of search, node filtering, timestamp show
Just append to html element and that's all

It's temporary solution till real frontend is implemented.