-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add signal API alerting #805
Conversation
doc/SetupRSync.md
Outdated
|
||
# Step 3: Networking | ||
If you have a firewall between the server and teslausb you will need to allow ports 22 and ICMP. | ||
Port 22 is used for the rsync service | ||
ICMP is used to verify the archive is reachable from teslausb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't appear to have anything to do with adding Signal notifications?
(the bit about icmp is also no longer correct)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're still adding a new empty line to this file.
This file shouldn't be part of the PR at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure SetupRSync.md isn't part of the PR, and that any shellcheck errors are addressed.
run/send-push-message
Outdated
function send_signal () { | ||
log "Sending Signal message." | ||
|
||
curl -X POST -H "Content-Type: application/json" $SIGNAL_URL'/v2/send' \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"$SIGNAL_URL/v2/send"
is easier to read and should avoid the shellcheck error
No description provided.