### requirements
* one or more eno hardware nodes (Beaglebone Black + a Fona module)
* Python 2.7
### installation
```shell
$ pip install eno
```
### usage
A cluster of eno hardware nodes are setup
with network connectivity to a testing machine.
The testing machine uses `eno.nodes.Node` to control the connected nodes
and to read data from them.
The nodes themselves run the `eno.server.app`.
Other clients (like the testing machine) connect to this server
to give instructions to the hardware and to read data back.
The hardware uses [python-gsmmodem](https://github.com/faucamp/python-gsmmodem)
to communicate with the onboard GSM modem.
The testing machine should have an `~/.enorc` describing the test cluster:
```yaml
- name: node A
ip_address: 192.168.1.102
sim: endaga
- name: node B
ip_address: 192.168.1.105
sim: endaga
- name: node C
ip_address: 192.168.1.107
sim: ting
phone_number: 19195551234
```
See additional examples in `server.py` and `sample_test.py`.
### license
MIT
### releases
* 0.0.5 - adjusts package structure
* 0.0.4 - adds missing requests requirement
* 0.0.3 - adjusts server script filename
* 0.0.2 - adds SMS handling capabilities
* 0.0.1 - barebones setup for pypi
### release process
you need a `~/.pypirc` like this:
```
[distutils]
index-servers =
pypi
[pypi]
repository: https://pypi.python.org/pypi
username: yosemitebandit
password: mhm
```
bump the versions in `setup.py` and here in the readme, then run:
```shell
$ git tag 0.0.1 -m 'eno-python v0.0.1'
$ git push origin master --tags
$ python setup.py sdist upload -r pypi
```
Metadata
Release files for eno 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| eno-0.0.5.tar.gz | 4.6 kB | Without provenance | Details for eno-0.0.5.tar.gz |
Release files / eno-0.0.5.tar.gz
| Download URL | eno-0.0.5.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
19cd7270976166295c342ef450f2ca1ef4799b1abd8859c1f19ef0f8c192d907
|
|
BLAKE2b-256 checksum How to use checksums |
872ef37c4a28ca9ac73001af3bc9aba8bc2e5b983429683bdf173c52bc8a9413
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for eno 0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.