shosai
supporting tool, management stock type document(not flow type document).
config
please, setup $HOME/.config/shosai/config.json, like below.
{
"docbase": {
"teamname": "<team name>",
"token": "<token>",
"username": "<username>"
},
"hatena": {
"blog_id": "<username>.hatenablog.com",
"client_id": "<client id>",
"client_secret": "<client secret>",
"consumer_key": "<consumer key>",
"consumer_secret": "<consumer secret>",
"hatena_id": "<hatena id>",
}
}
push article
$ shosai docbase push docs/xxx.md
upload (or update) article
(the document has images , uploading ones as attachment files)
pull article
$ shosai docbase pull docs/xxx.md
update local article (using this command, when managed article is already downloaded)
clone article
$ shosai docbase clone https://<teamname>.docbase.io/posts/xxxxxx --name xxx.md
download article
search article
$ shosai docbase search
getting recently uploaded documents
0.0.4
–verbose option
rfind, when finding mapping.json
0.0.2
fix bug for docbase, treating metadata (scope, groups, draft)
0.0.1
first release
Metadata
Release files for shosai 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| shosai-0.0.4-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for shosai-0.0.4-py2.py3-none-any.whl |
Release files / shosai-0.0.4-py2.py3-none-any.whl
| Download URL | shosai-0.0.4-py2.py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
76c96630675cae0f1bc53ba379e18cb9101eb13622904dc5276178518824d741
|
|
BLAKE2b-256 checksum How to use checksums |
388b6b9e2f5db9fdd5387c13b6dd23a85c1eb0988ebf613a830b8b061423be10
|
| 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.32.2 CPython/3.7.3
|
Security for shosai 0.0.4
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.