customjson 
This tool generates the "master" files that are used for the custom_updater and the custom_component_store
For the custom_updater it generates and update these jsonfiles:
For the custom_component_store it generates and updates ludeeus/data/custom-component-store/V1
Install
Require Python version 3.5.3+
python3 -m pip install -U customjson
Example
customjson --token aaabbbccc111222333 --mode component
CLI options
| param | alias | description |
|---|---|---|
--token |
-T |
An GitHub access_token with repo permissions. |
--push |
-P |
Push a new repos.json file to the information repo. |
--mode |
-M |
Must be card or component. |
--version |
-V |
Print the installed version. |
Add more resources
Components
The easiest way to add additional resources is to reuse the json file used by 'custom_updater' if yo have that.
Examples:
But there are other ways if you look in the /customjson/components/ dir you can see different implementations that give more granular control.
cards
look in the /customjson/cards/ dir to see different implementations
1 maintainer
Metadata
1 maintainer
Release files for customjson 2.13.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 | |
|---|---|---|---|---|
| customjson-2.13.1.tar.gz | 9.0 kB | Without provenance | Details |
Release files / customjson-2.13.1.tar.gz
| Download URL | customjson-2.13.1.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68ac36f7f7182f1ffb590bb53eb095985989770cfb17afa61cf523587ae77cd3
|
|
BLAKE2b-256 checksum How to use checksums |
db628a82ba222f71663be6a32f87c6c0160daeeb4886342449d64bbefcf26fea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.3
|
Security for customjson 2.13.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.
