bravetechnologycoop / bravebuttons Goto Github PK

Migration script currently requires user input from a read to give a name and other details to an installation. Instead this should be supplied as command line arguments, this will make it so we can run the script on Travis

re-organize Google Drive
Screen record a system deployment
Create a checklist for an installation (Enclosure building, Button pairing, Range Testing)

Where we check for:
Certificate validity
Deploy updates
Check Microsoft Flow

Log files keep growing to an unmanageable size, we want to prevent this.

Changing the SSH port to a non-conventional number will assist in botnets trying to bruteforce logins and wasting resources. Fail2ban would also assist in making sure brute force attempts are banned quick with their packets dropped so no I/O is used on logging thus preserving the SD card longer.

We aren't testing the fallback phone number functionality with the current test harness, and doing so requires having more than the single test phone number that twilio provides us. The goal for this issue is to set up a small mocked version of the twilio API to be able to test this.

In heartbeat.py, we catch and print an exception every time the scipt makes a call to darkstat before darkstat is up and running. Previously, this uncaught exception was causing the program to crash at startup.

Simply catching the exception and printing it to the log works fine for now, but we may want to handle it better

Using random numbers can cause collisions inadvertently which would lead to data loss. Also you lose context. Here are some suggestions.

If random, use a UUID.

import { v4 as uuidv4 } from 'uuid';
const outputFile = `./pairing-tool-output-${uuidv4().replace("-","")}.csv

Use the unix timestamp to identify when the pairing tool was ran in the filename.

const outputFile = `./pairing-tool-output-${Date.now() / 1000 | 0}.csv

If nanosecond timing is wanted with the timestamp idea, node provides this.

const hrTime = process.hrtime();
const curMicroseconds = hrTime[0] * 1000000000 + hrTime[1];
const outputFile = `./pairing-tool-output-${curMicroseconds}.csv

Following the instructions so far yields this error at the end:

"Job for networking.service failed because the control process exited with error code.
See "systemctl status networking.service" and "journalctl -xe" for details."

typing in journalctl -xe yields the following:

systemctl status networking.service yields

looks like a problem with 'add bridge' (is that bridge-utils?). I updated it and still have the same issue.

It appears the pairing tool when it comes to a mass deployment could get quite annoying as you are having to enter data per button.

As a suggestion, for 'mass-deploys', it would be a good idea to be able to provide a file such as:

# SITE: The Building
# Provide suite number followed by phone number for all buttons.
1704, 7785551234
59, 334324152
Common Room, 911

Then upon running the pairing tool with this file as input, it will just ask "Please pair button for Room: that calls ." then once it's paired, just move on to the next. This could help reduce installation times as well, on top of that there may be a way to automate the buttons being configured to hit the right endpoints after to reduce LoE per button install.