Telegram notification service

Parad0x d87c3176a4 Added '/help' command hace 5 años
src d87c3176a4 Added '/help' command hace 5 años
systemd-unit 9c018d3a86 - Updated totify`s unit file to support enable hace 5 años
.gitattributes 8fdc1faa82 - Moved to typescript hace 5 años
.gitignore 215808bbec - Add packaging script hace 5 años
LICENSE.md 492c8b3f2c - Fixed license author and year hace 5 años
README.md c9a92388fc - README.md updated with build section hace 5 años
TODO 6a07c9e4d2 - Added TODO hace 5 años
client.js eae00e2109 - Updated dev client script hace 5 años
package-lock.json d9aa6d3b47 - Removed nodemon and empty settings hace 5 años
package.json d9aa6d3b47 - Removed nodemon and empty settings hace 5 años
pkg.sh 457ebf151e - Fixed pkg.sh script final cwd hace 5 años
tsconfig.json 8fdc1faa82 - Moved to typescript hace 5 años

README.md

Totify

Simple communication bridge between clients and telegram. Using sockets is simple way for other clients to send notification. Current version support only one way communication (from client to telegram) but it should be possible to implement registering command. Protocol is based on queue where elements are separated with semicolons.

Build

npm install
npm run build

Start

npm start

Protocol Operations

register (name)

Reply with "<id>&<auth>"

register;Test App;

login (authcode)

Reply with "OK" on success or "ERR" with message;

login;PIZS-4681-bKUp-2154;

notify (msg)

Need authentication Reply with "OK" on success or "ERR" with message;

notify; test notification;

ping

Reply with pong

ping;

close

Reply with closing message and close connection

close;

Communication Sample

Server in: register;Test App;close;
Server out: 5&GSFBT-665-oJDDKqerYCWwfmtFWOOD;
Server in: login;EDSPG-466-VlyoDV9i6mBOAwle0hZU;ping;notify;Test;close;
Server out: OK;pong;OK;Closing connection;
Server in: login;invalid-code;
Server out: ERR;auth unmatched or not activated;
Server in: notify;notify without login;
Server out: ERR;need to be logged;