Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

trimarlib-brio

Basic Remote Input/Output - Python application

Getting started

These instructions will get you a copy of the project on your local machine for development and testing purposes. See Deployment for notes on how to deploy the project on a live system.

Prerequisites

The build process requires some basic development tools:

  • make - GNU Make program, either for *nix or Windows system, used to execute build and test targets
  • git - used not only to clone the repository, but also in auto-versioning (see Versioning)
  • python3

Two standard Python packages are used for build and installation steps:

  • setuptools
  • wheel

The application depends on the following libraries:

  • trimarlib-sysfsgpio
  • trimarlib-newland
  • json-rpc

These dependencies are defined in the setup.py installation script and therefore should be automatically satisfied by pip.

Building and releasing

Invoking make all (default target) prepares archives for distribution. It is done in two steps:

  1. query Git repository for tags (git describe command) to determine current version and generate version.py file,
  2. invoke Python interpreter passing setup.py script to prepare source and wheel distributions.

The Python interpreter invoked by the Makefile defaults to python - it is possible to override it passing a PYTHON variable to the command, e.g. make all PYTHON=python3.

The release process is automated and based on GitLab CI/CD environment - each commit triggers a build job which attempts to make and install built packages. If the commit is tagged, the built wheel distribution is passed to the deployment stage and the runner attempts to upload the package to the repository specified in project settings.

Deployment

Installation via pip (i.e. pip install trimarlib-brio) is the recommended method of deployment.

After the package has been installed it is recommended to perform additional steps:

  1. Install gpio-exporter.service and gpio.rules - see sysfsgpiolib project for more information;
  2. Install brio.service and brio.ini configuration file.

The second step is performed using the entry points exposed by the package:

  • brio-install-service - copies the predefined service file to /etc/systemd/system/brio.service, reloads systemd daemons and enables the service. Run brio-install-service -h for more information;
  • brio-install-configuration - copies the default configuration file to the default location. Run brio-install-configuration -h for more information.
  • brio-install - performs the above steps in one go. Run brio-install -h for more information.

The application is started using another entry point - brio-app. Run brio-app -h for more information.

Versioning

The project is versioned using a simple pattern based on repository tagging feature. See Makefile for implementation details, for versions available see tags on this repository.

Usage

See docstrings for API documentation.

Example of using the server in a custom application:

from brio import Server
import time


server = Server()
server.configure()
server.start()
time.sleep(10)
server.stop()

The application is run using the brio-app entry point, see Deployment for more information.

License

This software is licensed under the MIT License - see LICENSE.


This software conforms to the JSON RPC protocol, see website for more information.

Metadata

Release files for trimarlib-brio 0.1.0rc2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for trimarlib-brio 0.1.0rc2
File Interpreter ABI Platform
trimarlib_brio-0.1.0rc2-py3-none-any.whl Python 3 none any Details

Release files / trimarlib_brio-0.1.0rc2-py3-none-any.whl

Download URL trimarlib_brio-0.1.0rc2-py3-none-any.whl
Size 12.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
44c5a9d48fca38c5ae39044196363b2d41b2a75e2426403fb4ec76e1802c3f1f
BLAKE2b-256 checksum
How to use checksums
a5f2787fe3af1edbca6da79b4d7d60cc9f959fc532b2043e7625fc98f1587da6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.4
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page