CGMiner HTTP Interface
A basic HTTP endpoint to any API conforming to the CGMiner RPC interface.
Installation
From pip:
$ pip install cgminerhttpinterface
Usage
Most people will just want to run the server, which means a simple command in your shell / command prompt:
$ chi-server
This will start an HTTP server reachable on all interfaces on port 8080, which will re-issue incoming requests to localhost:4028 (the default host:port for the CGMiner RPC API.) This server can be started at any time, but will of course only be useful once the CGMiner API has been started.
Options
usage: chi-server [-h] [-w HTTP_PORT] [-p API_PORT] [-a API_HOST]
Start HTTP interface to the monitoring API
optional arguments:
-h, --help show this help message and exit
-w HTTP_PORT, --http_port HTTP_PORT
Port to use for http server
-p API_PORT, --api_port API_PORT
Port used by API server
-a API_HOST, --api_host API_HOST
Host name/address used by API server
Using the HTTP Interface
URL structure is http://<host>[:port]/<command>[+command…]/[parameter]. For example:
http://localhost/summary+pools/ : combined summary and pools report on the default port
http://localhost:8081/gpu/0 : single gpu status on port 8081 (as defined in the command line)
Visiting the server root (e.g. http://localhost/) will issue the compound ‘summary+devs’ command.
At this point in time, the HTTP endpoint will simply serve the response of the API as is - meaning a JSON formatted data structure containing sections for each command issued. All commands available via the CGMiner API are also available via the HTTP endpoint - in fact the HTTP endpoint performs no command validation at all, relying on the API to validate requests and respond appropriately.
Metadata
Release files for cgminerhttpinterface 0.1.3
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 |
|---|---|---|---|---|
| cgminerhttpinterface-0.1.3.tar.gz | 4.4 kB | Without provenance | Details for cgminerhttpinterface-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cgminerhttpinterface-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for cgminerhttpinterface-0.1.3-py3-none-any.whl |
Total release size: 14.0 kB
Release files / cgminerhttpinterface-0.1.3.tar.gz
| Download URL | cgminerhttpinterface-0.1.3.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2becec9ba8fcc3916a6e5537847b025dae869bc3503b7a77e5cacdde16b87244
|
|
BLAKE2b-256 checksum How to use checksums |
7b9afb493975cd59ed69ea764a0a384cc5919d81c7279b8a830b04d9acd0bc03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Release files / cgminerhttpinterface-0.1.3-py3-none-any.whl
| Download URL | cgminerhttpinterface-0.1.3-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5578c2478cd8ede6cb8138803d3945d5bfc947d9cd37f0809b1be853aecb6de
|
|
BLAKE2b-256 checksum How to use checksums |
49f0539dd6697ec74d069e685c4ea354437d505f6127f3599d1c418b176dd42a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Security for cgminerhttpinterface 0.1.3
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.