PLATER
PLATER is a service to stand up REST endpoint over a neo4j or redis graph database. There are some restrictions on the data structure of the Neo4j backend to be fully utilized through PLATER.
Data structure restrictions:
- All nodes should have an
idto be searchable (Used in querying single Nodes)- All edges should have an
idto be searchable (Used in generating ReasonerAPI)- Data is recommended to comply to the Translator Reasoner API.
Installation
To run the web server directly:
Create a virtual Environment and activate.
cd <PLATER-ROOT>
python<version> -m venv venv
source venv/bin/activate
Install dependencies
pip install -r PLATER/requirements.txt
Configure PLATER settings
Populate .env-template file with settings and save as .env in repo root dir.
WEB_HOST=0.0.0.0
WEB_PORT=8080
DB_HOST=<neo4j_or_redis_address>
DB_USERNAME=<user name required for neo4j, empty for redis>
DB_PASSWORD=''
DB_PORT=<redis port or neo4j http port>
DB_NAME=<db name for redis, uses default db for neo4j>
DB_TYPE=<use values 'redis' or 'neo4j'>
PLATER_TITLE='Plater'
PLATER_VERSION='1.0.0'
Run Script
./main.sh
DOCKER
Or build an image and run it.
cd PLATER
docker build --tag <image_tag> .
cd ../
docker run --env-file .env\
--name plater\
-p 8080:8080\
--network <network_where_neo4j_is_running>\
plater-tst
Clustering with Automat Server [Optional]
You can also serve several instances of plater through a common gateway(Automat). On specific instructions please refer to AUTOMAT's readme
Miscellaneous
/about Endpoint
The /about endpoint can be used to present meta-data about the current PLATER instance.
This meta-data is served from <repo-root>/PLATER/about.json file. One can edit the contents of
this file to suite needs. In containerized environment we recommend mounting this file as a volume.
Eg:
docker run -p 0.0.0.0:8999:8080 \
--env DB_HOST=<your_db_host> \
--env DB_PORT=<your_db_port> \
--env DB_USERNAME=<db_user_name required for neo4j, ignored for redis> \
--env DB_PASSWORD=<db_password> \
--env DB_NAME=<required for redis> \
--env DB_TYPE=<redis or neo4j> \
--env WEB_HOST=0.0.0.0 \
-v <your-custom-about>:/<path-to-plater-repo-home>/plater/about.json \
--network=<docker_network_neo4j_is_running_at> \
<image_tag>
Metadata
Release files for PLATER-GRAPH 1.9.8
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 | |
|---|---|---|---|---|
| PLATER-GRAPH-1.9.8.tar.gz | 27.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| PLATER_GRAPH-1.9.8-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 59.2 kB
Release files / PLATER-GRAPH-1.9.8.tar.gz
| Download URL | PLATER-GRAPH-1.9.8.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43c5821f2ff567b239a593af9089a22510b3534ac833c39e7c041d91a1f7634a
|
|
BLAKE2b-256 checksum How to use checksums |
d77ebceebc4d23300f679df7474cb4602d5db228c1d877f24aab363310d7ac22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Release files / PLATER_GRAPH-1.9.8-py2.py3-none-any.whl
| Download URL | PLATER_GRAPH-1.9.8-py2.py3-none-any.whl |
|---|---|
| Size | 31.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
8bb4769979d91eeeae16b2e7790e53ccf1efe0a653ce3123a194b349c54ffff2
|
|
BLAKE2b-256 checksum How to use checksums |
b7b730c7b29533ba1dfaeaa75c9582c9d7019ee6f79a3c86b5cbda9de422063e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Security for PLATER-GRAPH 1.9.8
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.