Harness TUI
A Textual App that allows you to interact with your Harness account.
Installation
Prerequisites
- Python 3.9 or higher
- Pipx (optional, but recommended)
Using pipx
The recommended way to install the app is to use pipx. This will install the app in an isolated environment and make it available globally.
pipx install harness-tui
Using pip
You can also install the app using pip. This will install the app in the user's environment.
# Optionally create a virtual environment for the tool
# python -m venv /opt/harness-tui/.venv
# source /opt/harness-tui/.venv/bin/activate
pip install harness-tui
# echo "export PATH=\$PATH:/opt/harness-tui/.venv/bin" >> ~/.bashrc
Development
- Clone the repository
- Run
make install-devto create a virtual environment and install the dependencies - Run
source .venv/bin/activateto activate the virtual environment
Using direnv
As an alternative to manually activating the virtual environment, you can use direnv. To do so, follow these steps:
- Install direnv:
brew install direnv - Add the following line to your shell configuration file (e.g.
~/.bashrc,~/.zshrc):eval "$(direnv hook bash)" - Create a
.envrcfile in the project root with the following content:
export VIRTUAL_ENV=.venv
dotenv
layout python
- Run
touch .envto create the.envfile - Run
direnv allowto allow the.envrcfile
Now the virtual environment will be activated automatically when you cd into the project directory. Furthermore all environment variables defined in the .env file will be loaded.
Developing the app
Refer the textual docs and the harness API docs for most of the information we need to develop the app.
Running the app
To run the app, you can use the make run command. This will start the app in the terminal.
Alternatively, just run the app directly:
python src/harness_tui/app.py
Up to date dependencies
If the requirements file has been updated, you can run make install-dev to update the dependencies in the virtual environment.
Roadmap
We will graduate the project from a requirements txt managed project to a poetry managed project with a pyproject.toml that will allow us to publish the project to PyPi for distribution.
Metadata
Release files for harness-tui 0.1.2
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 | |
|---|---|---|---|---|
| harness_tui-0.1.2.tar.gz | 19.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| harness_tui-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.3 kB
Release files / harness_tui-0.1.2.tar.gz
| Download URL | harness_tui-0.1.2.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccb24fb91976b62dcea420ae2516485d559c99fce47dcd7375b3e502e27d2ad0
|
|
BLAKE2b-256 checksum How to use checksums |
af2d19aa73941aa03c4ca32c5d8ef6f246df3a6d87d3faae2ad1d278b938d21f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.9 Darwin/23.1.0
|
Release files / harness_tui-0.1.2-py3-none-any.whl
| Download URL | harness_tui-0.1.2-py3-none-any.whl |
|---|---|
| Size | 24.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08d2c5f05c65b6eaacdfc5d681ee1de59fed05e0025e1cc03b7350629cd1f6e3
|
|
BLAKE2b-256 checksum How to use checksums |
8b09dfa70ff59cec38a15fe8272b466d324b75dbf282cc098e74aae5bea04d4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.9 Darwin/23.1.0
|
Security for harness-tui 0.1.2
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.