diff options
| author | Simeon Simeonov | 2014-08-31 13:28:22 +0200 |
|---|---|---|
| committer | Simeon Simeonov | 2014-08-31 13:28:22 +0200 |
| commit | 472f3d3bf50b352165bc192ce5d0ffa45d81ce00 (patch) | |
| tree | 56d35f027b7939284871a10a57223a768b738f51 /README | |
| parent | fa1aacfde8679551cebda346a2c45d04204441eb (diff) | |
Version 1.0 completed
Diffstat (limited to 'README')
| -rw-r--r-- | README | 46 |
1 files changed, 37 insertions, 9 deletions
| @@ -27,6 +27,9 @@ beinc_generic_client.py - a simple client used to push notification messages | |||
| 27 | Why should I use BEINC and what has it done for me lately? | 27 | Why should I use BEINC and what has it done for me lately? |
| 28 | ---------------------------------------------------------- | 28 | ---------------------------------------------------------- |
| 29 | 29 | ||
| 30 | BEINC is a free-software, licensed under the GPL3. It gives you the freedoms | ||
| 31 | of using it, studying it and modifying it. | ||
| 32 | |||
| 30 | BEINC is designed to assist you two common scenarios. | 33 | BEINC is designed to assist you two common scenarios. |
| 31 | As an example we will consider the case of an IRC cliet, although BEINC can be | 34 | As an example we will consider the case of an IRC cliet, although BEINC can be |
| 32 | used by any client that conforms with BEINC's "messaging protocol". | 35 | used by any client that conforms with BEINC's "messaging protocol". |
| @@ -35,9 +38,15 @@ We have the common situation where a user is accessing an IRC client located on | |||
| 35 | a different computer (typically: weechat, irssi, etc. running on a remote server) | 38 | a different computer (typically: weechat, irssi, etc. running on a remote server) |
| 36 | The IRC client receives a private message (or any event that requires the user's | 39 | The IRC client receives a private message (or any event that requires the user's |
| 37 | attention) and the user has to be notified. | 40 | attention) and the user has to be notified. |
| 41 | No matter which of the two scenarios applies to your needs, you should start by | ||
| 42 | - setting up a BEINC client similar to beinc_generic_client.py on the server | ||
| 43 | If you are running weechat >=0.4.0, this version of BEINC comes with | ||
| 44 | a complete weechat BEINC-client: beinc_weechat.py | ||
| 45 | Configure the client to send notifications to the beinc_server.py | ||
| 46 | N.B. Using encryption is important in these days and age. | ||
| 38 | 47 | ||
| 39 | Scenario one: | 48 | Scenario one: |
| 40 | The user's computer can be reached from the server running the IRC client. | 49 | The user's computer can be reached by the server running the IRC client. |
| 41 | If the server (running the IRC client) is able to connect to | 50 | If the server (running the IRC client) is able to connect to |
| 42 | a specified TCP port on the user's computer, this is sufficient for BEINC to | 51 | a specified TCP port on the user's computer, this is sufficient for BEINC to |
| 43 | directly notify the user. Solution: | 52 | directly notify the user. Solution: |
| @@ -45,25 +54,44 @@ directly notify the user. Solution: | |||
| 45 | notification-message should be displayed). Define an unprivileged port for | 54 | notification-message should be displayed). Define an unprivileged port for |
| 46 | beinc_server.py to listen on and enable its OSD capabilities | 55 | beinc_server.py to listen on and enable its OSD capabilities |
| 47 | (through pynotify and/or pyosd) | 56 | (through pynotify and/or pyosd) |
| 48 | - set up a BEINC client similar to beinc_generic_client.py on the server | ||
| 49 | If you are running weechat >=0.4.0, this version of BEINC comes with | ||
| 50 | a complete weechat BEINC-client: beinc_weechat.py | ||
| 51 | Configure the client to send notifications to the beinc_server.py | ||
| 52 | 57 | ||
| 53 | Scenario two: | 58 | Scenario two: |
| 59 | The user's computer can NOT be reached by the server running the IRC client. | ||
| 60 | This scenario is typical for users that are working on computers that can not | ||
| 61 | be reached from outside. | ||
| 62 | Solution: | ||
| 63 | - find a server that can be reached by the server running the IRC client. | ||
| 64 | - set up the beinc_server.py on it. No OSD capabilities are needed (no X11). | ||
| 65 | Define instance(s) for queueing. Define a queue size | ||
| 66 | (how many notifications to store) for each of them. | ||
| 67 | - set up beinc_poller.py on the desktop workstation (the computer where the | ||
| 68 | notification-message should be displayed). | ||
| 69 | beinc_poller.py should be able to access the server running beinc_server.py | ||
| 70 | Polling interval of 5 seconds should be enough for most users. | ||
| 54 | 71 | ||
| 72 | Read beinc_config_sample.json.readme for details on how to setup beinc_server.py | ||
| 73 | and beinc_weechat.py! | ||
| 74 | Use "-h" command line parameter in order to display the available options for | ||
| 75 | beinc_poller.py and beinc_generic_client.py | ||
| 55 | 76 | ||
| 56 | 77 | ||
| 57 | Supported systems & requirements | 78 | Supported systems & requirements |
| 58 | -------------------------------- | 79 | -------------------------------- |
| 59 | Any system running Postfix and Spamassassin. | 80 | Any system running the software required for the selected components. |
| 81 | All components tested on: Gentoo GNU/Linux 2013,2014, | ||
| 82 | Ubuntu GNU/Linux 14.4,13.10, | ||
| 83 | FreeBSD 9.x | ||
| 60 | 84 | ||
| 61 | 85 | ||
| 62 | Requirements: | 86 | Requirements: |
| 63 | All components: Python 2.7.* | 87 | All components: Python 2.7.* |
| 64 | beinc_server.py: cherrypy >= 3.2.0, pyopenssl >= 0.13.0 | 88 | beinc_server.py: cherrypy >= 3.2.0, pyopenssl >= 0.13.0 (opntional (ssl support)), |
| 65 | beinc_weechat.py: | 89 | pynotify >= 0.1 (optional), pyosd >= 0.2 (optional) |
| 66 | beinc_poller.py: | 90 | beinc_weechat.py: Weechat >= 0.4.0 |
| 91 | beinc_poller.py: pynotify >= 0.1 (optional), pyosd >= 0.2 (optional) | ||
| 92 | beinc_generic_client.py: No additional software required | ||
| 93 | |||
| 94 | Read INSTALL for more details about installing the requirements! | ||
| 67 | 95 | ||
| 68 | 96 | ||
| 69 | License | 97 | License |
