The purpose of these tools is to serve the witnesses and assist them
with their regular ground work of managing events on the PeerPlays
blockchain.
## Development use
Clone the develop branch from the repository locally
git clone -b remote git@bitbucket.org:peerplaysblockchain/bookied-ui.git
Install environment
$ apt-get install -y python3 python3-pip libmysqlclient-dev libssl-dev npm
$ npm install -g bower
Install virtual environemnt user either one of the following
$ pip3 install virtualenv # should always works
$ apt-get install python-virtualenv # Ubuntu 14.04
$ apt-get install virtualenv # Ubuntu 16.04
Install static files
$ cd app
$ bower install
Run the development server
$ run_dev_server.sh
The manual intervention module is then available at
http://localhost:5000/overview
For documentation of usage please look inside the scripts. To add the init accounts please use
5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
### Description of scripts
setup.sh
Ensures that the given command is executed within a virtual environment
run_dev_server.sh
Starts the manual intervention module via flask development webservice
## Docker
### Build and Run Docker Container
$ cd bookied-ui
$ docker build -t boss:latest .
$ docker-compose up
.. then open browser with URL:
http://localhost:8000
1 maintainer
Metadata
1 maintainer
Release files for bos 0.0.1
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 | |
|---|---|---|---|---|
| bos-0.0.1.tar.gz | 2.3 kB | Without provenance | Details |
Release files / bos-0.0.1.tar.gz
| Download URL | bos-0.0.1.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2807eef6d713162e21d50603bf040311a9e9891fc5c8a9c35abd5213de2a4f2
|
|
BLAKE2b-256 checksum How to use checksums |
fb0220f45c3d650e29c7c150bdaf7592cfc14211c7ef4920cc3ad2a4ac6834db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bos 0.0.1
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.
