ShaYmez/HBmonitor
1
0
Fork 0
mirror of https://github.com/ShaYmez/HBmonitor.git synced 2024-12-22 17:45:37 -05:00
Code Issues Projects Releases Wiki Activity
2 Commits 4 Branches 0 Tags 1,009 KiB
Python 55.8%
HTML 38.3%
PHP 5.2%
Shell 0.7%
ef534b58d0
Go to file
Cort Buffington ef534b58d0 Formatting Update – FULLY FUNCTIONAL NOW
2018-06-22 15:11:07 -05:00
templates Initial Commit 2018-06-22 09:34:14 -05:00
.gitignore Initial Commit 2018-06-22 09:34:14 -05:00
config_SAMPLE.py Initial Commit 2018-06-22 09:34:14 -05:00
index_template.html Formatting Update – FULLY FUNCTIONAL NOW 2018-06-22 15:11:07 -05:00
logfile.log Initial Commit 2018-06-22 09:34:14 -05:00
README.md Initial Commit 2018-06-22 09:34:14 -05:00
requirements.txt Initial Commit 2018-06-22 09:34:14 -05:00
web_tables.py Initial Commit 2018-06-22 09:34:14 -05:00

README.md

Please join the DVSwitch group at groups.io for online forum support, discussion, and to become part of the development team. DVSwitch@groups.io
### FOR SUPPORT, DISCUSSION, GETTING INVOLVED ### Please join the DVSwitch group at groups.io for online forum support, discussion, and to become part of the development team. DVSwitch@groups.io

Socket-Based Reporting for HBlink

Over the years, the biggest request recevied for HBlink (other than call-routing/bridging tools) has been web-based diagnostics and/or statistics for the program.

I strongly disagree with including the amount of overhead this would require inside HBlink -- which still runs nicely on very modest resources. That it does this, and is in Python is a point of pride for me... Just let me have this one, ok? What I have done is added some hooks to HBlink, which will be expanded over time, whereby it listens on a TCP socket and provides the raw data necessary for a "web dashboard", or really any external logging or statistics gathering program.

HBmonitor is my take on a "web dashboard" for HBlink.

THIS SOFTWARE IS VERY, VERY NEW

Right now, I'm just getting into how this should work, what does work well, what does not... and I am NOT a web applications programmer, so yeah, that javascript stuff is gonna look bad. Know what you're doing? Help me!

It has now reached a point where folks who know what they're doing can probably make it work reasonably well, so I'm opening up the project to the public.

GOALS OF THE PROJECT

Some things I'm going to stick to pretty closely. Here they are:

  • HBmonitor be one process that includes a webserver
  • Websockets are used for pushing data to the browser - no long-polling, etc.
  • Does not provide data that's easily misunderstood

0x49 DE N0MJS

Copyright (C) 2013-2018 Cortney T. Buffington, N0MJS n0mjs@me.com

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA