You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For those trying to get started, here's the steps I took:
You have to get your PulsePoint Agency ID. The easiest way I found to do that was to go to web.pulsepoint.com, search for an agency, and then look at the network inspector in your browser to see what agency_id it requests
I changed line 56 in setup.py from package_data= to license_package_data= to get around the name confliction warning
Because I wanted this sent to a TAK server, I created a user on my TAK server and copied over the .pem and .key file into the same directory as I was running pulsecot. Note that you have to make sure you remove the passphrase or you'll get a prompt for the password
PulseCOT wants the config.ini file to look basically like this. You need to replace AGENCY_ID, takserver and clientcert with what yours actually are:
For those trying to get started, here's the steps I took:
You have to get your PulsePoint Agency ID. The easiest way I found to do that was to go to web.pulsepoint.com, search for an agency, and then look at the network inspector in your browser to see what agency_id it requests
I changed line 56 in
setup.py
frompackage_data=
tolicense_package_data=
to get around the name confliction warningBecause I wanted this sent to a TAK server, I created a user on my TAK server and copied over the .pem and .key file into the same directory as I was running pulsecot. Note that you have to make sure you remove the passphrase or you'll get a prompt for the password
PulseCOT wants the
config.ini
file to look basically like this. You need to replaceAGENCY_ID
,takserver
andclientcert
with what yours actually are:(Note I have the above without the truststore cert, so I have don't verify enabled. You probably want to add in the appropriate configuration)
And viola! I was able to run
pulsecot -c config.ini
and see events populate locally and on my TAK server.The text was updated successfully, but these errors were encountered: