Generate Graphs from tinc
TODO
- currently the Maps api key is hard coded in
tinc_graphs/static/map.html, if you want to use this feature you will need to replace this key manually
Install
Nix
# tinc_pre is required:
nix-env -i -f tinc_graphs.nix
## e.g. in Retiolum:
## krebs.retiolum.tinc = pkgs.tinc_pre
Local
python setup.py install
# also install graphviz,imagemagic for building graphs
Usage:
see source of the 2 builder scripts:
#all-around-builder
# env: EXTERNAL_FOLDER, INTERNAL_FOLDER, GEODB, TINC_HOSTPATH
all-the-graphs
# build actual graphs
build-graph
# exported py scripts
tinc-stats2json # - parses tinc current state into json
tinc-build-graph # - transfers json to graph
copy-map # - copies map.html into $1
add-geodata # - adds geodata to json
tinc-availability-stats # adds availability data to json
Geodb infos
- http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
- nix-env -iA geolite-legacy
Upload to pypi
python setup.py sdist
twine upload dist/*
Metadata
Release files for tinc-graphs 0.3.11
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 |
|---|---|---|---|---|
| tinc_graphs-0.3.11.tar.gz | 11.7 kB | Without provenance | Details for tinc_graphs-0.3.11.tar.gz |
Release files / tinc_graphs-0.3.11.tar.gz
| Download URL | tinc_graphs-0.3.11.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea3a2462d2417feab7b54bc1295a6793448eb0d6f0a5451a1bde629eb5887b2a
|
|
BLAKE2b-256 checksum How to use checksums |
01e2bfed6d417b44d26844ddb9011921c94e73b5a89b327937f8e9101afa3603
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.5
|
Security for tinc-graphs 0.3.11
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.