semvec/pypi-packages huggingface dataset:
bme280_exporter 0.1.0
Prometheus exporter for the Bosh BME280 sensor
License: MIT
Keywords: raspberry pi

bme280_exporter
===============

Python Prometheus exporter for the Bosch BME280 sensor

Requirements
------------

-  `Adafruit_Python_BME280 <https://github.com/adafruit/Adafruit_Python_BME280>`__

Installation
------------

.. code:: bash

    pip install bme280_exporter

Usage
-----

.. code:: bash

    $ bme280_exporter -h
    usage: bme280_exporter [-h] [-v] [-p PORT] [-a ADDRESS] [-l LABELS]
                           [-i INTERVAL] [-f FILTER] [-ho HO] [-po PO] [-to TO]

    optional arguments:
      -h, --help            show this help message and exit
      -v, --verbose         increase output verbosity
      -p PORT, --port PORT  exporter port (default: 9500
      -a ADDRESS, --address ADDRESS
                            BME280 I2C address (default: 0x77)
      -l LABELS, --labels LABELS
                            JSON object of Prometheus labels to apply
      -i INTERVAL, --interval INTERVAL
                            measurement sample interval (default: 2)
      -f FILTER, --filter FILTER
                            filter value to apply (0-4, default: 0)
      -ho HO                humidity oversampling value (1-5, default: 4)
      -po PO                pressure oversampling value (1-5, default: 4)
      -to TO                temperature oversampling value (1-5, default: 4)

Docker
------

.. code:: bash

    docker pull ashtreefarms/bme280-exporter-rpi
    docker run -p 9500:9500 --device /dev/i2c-1 ashtreefarms/bme280-exporter-rpi \
               --labels '{"zone": "bedroom"}'

MIT License
===========

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
“Software”), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
elastic-companion 5.1.0
Useful commands for Elasticsearch
License: MIT
Keywords: elasticsearch cli

elastic-companion
=================

A command-line tool and API for various Elasticsearch operations.

.. image:: https://travis-ci.org/getconversio/elastic-companion.svg?branch=master
    :target: https://travis-ci.org/getconversio/elastic-companion

Install
-------

    pip install elastic-companion

**Note**: The 1.X versions of elastic-companion support Elasticsearch 1.X and
the 5.X versions support Elasticsearch 5.X. This is similar to the versioning
of the official library

Commands
--------

To see the list of commands, use the ``-h`` or ``--help`` flag.

Each command has a corresponding Python module that can be imported and used as
an API rather than from the command-line.

### `setup`

The `setup` command will load all indexes, mappings, templates and scripts from the data directory, and send them to ES.

#### `/scripts`

The scripts folder should have `.json` files which act as script descriptors. Each file should have the content:

```json
{
    "id": "SCRIPT_ID",
    "lang": "SCRIPT_LANG",
    "body": "SCRIPT_BODY",
    "path": "SCRIPT_BODY_FILE_PATH"
}
```

While `id` and `lang` are required and should match the requirements of ES. These will determine how each script is stored. The values `body` and `path`, however, are mutually exclusive and only one is required. You can specify the script's body directly inline under `body`, or point to a file using `path`.

Developing
----------

If you are using Docker and Docker Compose, then you don't need to fiddle with
python and pip manually. Otherwise, see below.

Download Python 3, then::

    $ pyvenv-3.X venv
    $ source venv/bin/activate
    $ pip3 install -r requirements.txt
    $ ./cli.py -h

On Ubuntu, there's a bit of an issue with ``pip3`` and the above might not work.
Then::

    $ pyvenv-3.X venv --without-pip
    $ source venv/bin/activate
    $ cd venv
    $ wget https://bootstrap.pypa.io/get-pip.py
    $ python3 get-pip.py
    $ cd ..
    $ pip3 install -r requirements.txt
    $ ./cli.py -h

Testing
-------

Use ``nose``::

    $ nosetests

or::

    $ docker-compose run --rm companion nosetests

Deploying
---------

You need access to the pypi repository first, then it's just a matter of::

    $ python setup.py sdist bdist_wheel
    $ twine upload dist/*