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
Copy file name to clipboardExpand all lines: README.md
+14-17Lines changed: 14 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,13 @@ Current Version: 1.0.0
12
12
13
13
Description:
14
14
15
-
This application suite was designed by volunteer fire fighters to enhance the experience of First Responders during an emergency 911 callout. The main goal of this application is to provide a free suite of applications which can help fire fighters receive timely information and communicate activities with one another as incidents progress. This software is currently in use by some firehalls in the Prince George, BC Canada, Regional District. For contact information see the contact section at the bottom of this page.
15
+
This application suite was designed by volunteer fire fighters to enhance the experience of First Responders during an emergency 911 callout. The main goal of this application is to provide a free suite of applications which can help firefighters receive timely information and communicate activities with one another as incidents progress. This software is currently in use by some fire halls in the Prince George, BC Canada, Regional District. For contact information see the contact section at the bottom of this page.
16
16
17
17
Key Features:
18
18
-------------
19
19
- Real-time Email trigger (using Google App Engine) or email polling for 911 callouts received from your
20
20
Fire Operations Command Center. Easily adaptable to other callout trigger mechanisms (such as Web, Rest API, SMS, etc).
21
-
- Pluggable support for SMS gateway providers to send SMS information to fire fighters.
21
+
- Pluggable support for SMS gateway providers to send SMS information to firefighters.
@@ -31,12 +31,12 @@ Fire Operations Command Center. Easily adaptable to other callout trigger mechan
31
31
- 'SMS command mode' allows SMS users to respond to calls (useful if radios don't work or data is unreliable)
32
32
- Google Maps showing Distance from Firehall to Incident
33
33
- Self Installation available (see videos below)
34
-
- User Account management (LDAP support optional)
34
+
- User Account Management (LDAP support optional)
35
35
- Callout history with responding members
36
-
- Google charts shows statistical view of data as well as monthly and annual member participation.
36
+
- Google charts show a statistical view of data and monthly and annual member participation.
37
37
- Customizable user interface using twig templates (http://twig.sensiolabs.org/)
38
38
- Experimental Android App which integrates with the web application.
39
-
- Great backup system during power outages at your firehall (if installed offsite / cloud), still get callouts via cell phone when radio backup battery system fails or has poor coverage.
39
+
- Great backup system during power outages at your firehall (if installed offsite / cloud), but you still get callouts via cell phone when the radio backup battery system fails or has poor coverage.
40
40
- Secure features such as optional two factor authentication (2FA) support, new device login detection and brute force attack detection help keep admin and users informed about suspcious activity.
Next create a custom sms twig file in the root folder where config.php exists, inside a new folder
606
-
you wil lcreated named:
606
+
you will create named:
607
607
608
608
views-custom
609
609
@@ -620,15 +620,15 @@ https://vejvoda.com/rr/
620
620
{% endblock %}
621
621
622
622
This will use the website: https://vejvoda.com/rr/ as a proxy to forward requests to: https://svvfd.vsoft.solutions
623
-
which all phones would recognize because it uses the wellknown .com format
623
+
which all phones would recognize because it uses the well-known .com format
624
624
625
625
Development:
626
626
--------------
627
627
Rip Runner uses composer for dependency management. Currently php 8.x is supported and our continuous integration system (Github actions) runs automated tests on those versions. If you want to contribute to rip runner as a developer checkout the repo from github and from the php folder of the repo on your local system run:
628
628
629
629
composer install
630
630
631
-
This will download all runtime and automated tests dependencies. If compser completed successfully you should be able to run the automated tests by running this command from the php folder:
631
+
This will download all runtime and automated tests dependencies. If composer completed successfully you should be able to run the automated tests by running this command from the php folder:
632
632
633
633
phpunit
634
634
@@ -641,11 +641,11 @@ Experimental Work:
641
641
642
642
Angular client:
643
643
---------------
644
-
We have begun porting the user interface to Angular (v8+). Currently this UI is partially ported from the
644
+
We have begun porting the user interface to Angular (v8+). Currently, this UI is partially ported from the
645
645
legacy twig UI, in order to build and deploy to your server:
646
646
647
647
- Install Node.js® and npm (https://nodejs.org/en/download/) if they are not already on your machine.
648
-
- Install the Angular CLI globally, open a console prompt:
648
+
- Install the Angular CLI globally, and open a console prompt:
649
649
650
650
npm install -g @angular/cli
651
651
@@ -673,25 +673,22 @@ then copy the ngui folder to the root folder on svvfd.yourhost.com
673
673
674
674
Serverless support:
675
675
-------------------
676
-
We have started work on the application architecture to prepare for supporting various vendors who offer serverless computing platforms. Documentation can be read regarding deploying to Google Cloud Run (GCR) using a docker container
676
+
We have started work on the application architecture to prepare to support various vendors who offer serverless computing platforms. Documentation can be read regarding deploying to Google Cloud Run (GCR) using a docker container
Special thanks to all who have contributed to the success of this project. We accept patches and ideas from others and priortize based on time constraints and compatibility with our future direction.
682
+
Special thanks to all who have contributed to the success of this project. We accept patches and ideas from others and prioritize based on time constraints and compatibility with our future direction.
683
683
684
684
Contributors currently include:
685
685
- The Salmon Valley Fire Hall for all the great testing and feedback
686
686
- Dennis Lloyd (Officer at the Shell Glen Fire Hall) for peer review, and many contributions, without which
687
-
we would have many more defecs and have a much less pleasing user interface.
687
+
we would have many more defects and have a much less pleasing user interface.
0 commit comments