richbl / go-distributed-motion-s3 Goto Github PK

DOES:
Currently, the dashboard does not make any notifications when a client goes quiet (offline)

SHOULD:
While the dashboard already knows how to manage client non-report conditions, and displays that status using color, it should (optionally) also send a notification (e.g., email) when these non-report conditions occur

DOES:
Current dashboard (1.3.0) uses static HTML to display in browser. Must refresh the browser to view updated information.

SHOULD:
Dashboard should update dynamically (full-duplex) in real-time (or near real-time).

DOES:
Currently using IPV4 exclusively.

SHOULD:
Provide support for IPV6.

DOES:
Current implementation has the clients periodically "phone home" for server updates (needed to push client stats to DMS3 dashboard).

SHOULD:
Move to more of a pub/sub protocol, and then think about pushing client stats differently (maybe on a dashboard refresh, so only when needed).

Using golang 1.16 and 1.17.3

See the logs

xmaxmex@ubuntu:/go-distributed-motion-s3$ ls
cmd dms3build dms3dashboard dms3mail dms3server go.sum LICENSE ROADMAP.md
config dms3client dms3libs dms3_release go.mod INSTALL.md README.md
xmaxmex@ubuntu:/go-distributed-motion-s3$ /usr/local/go/bin/go run cmd/compile_dms3/compile_dms3.go
Creating release folder for linux_arm8 platform...
Creating release folder for linux_amd64 platform...
Creating release folder for linux_arm6 platform...
Creating release folder for linux_arm7 platform...
Creating release folder for dms3client component...
Creating release folder for dms3server component...
Creating release folder for dms3mail component...
Creating release folder for install_dms3 component...
Creating release folder for dms3client_remote_installer component...
Creating release folder for dms3server_remote_installer component...
Creating release folder for dms3libs component...
Creating release folder for dms3dashboard component...
Building dms3 components for linux_arm6 platform...
exit status 1
exit status 1
xmaxmex@ubuntu:~/go-distributed-motion-s3$

Any idea?

DOES:
User proxy sensing currently uses Wi-Fi only

SHOULD:
User proxy sensing should alternatively use Bluetooth connectivity (using RSSI, L2CAP, or similar)

DOES:
Currently, a DMS3Client is assumed to run on a Raspberry Pi, so the icon that's represented is the RPI logo.

SHOULD:
Should be able to configure the DMS3Client to include vendor type (e.g., Banana Pi, Orange Pi, etc.)

DOES:
Currently (1.3.0) have testing in place for some, but not all, libs (DMS3LIbs)

SHOULD:
Have complete code coverage for all libs in DMS3Libs

DOES:
No native support for OpenCV motion detection in DMS3

SHOULD:
Incorporate native OpenCV motion detection library with sample support

DOES:
Currently, the dashboard does not update the kernel release (e.g., 5.4.69-v7+) of the client endpoints.

SHOULD:
Permit the dashboard to query and display kernel release details, as this can be useful in tracking the overall health of active clients (can be useful as a prompt to make system updates/upgrades).

DOES:
Currently, no way to actually view events on the dashboard.

SHOULD:
Permit user to "drill down" into GUI and view event images.

Does: builds using legacy Go environment vars (e.g., GOPATH)

Should: follow updated idiomatic Go best practices (using Go modules dependency system)

DOES:
Currently, client events are displayed based on all available images found on the client.

SHOULD:
Permit filtering of images (by date, pixels change, etc.).