hausschrat cli
setup
Use pip to install.
pip3 install hausschrat --user
No magic here. That's all.
usage
The configuration file of hausschrat cli is located in ~/.config/hausschrat.yml.
At least a profile named default must be configured.
default:
server: http://localhost:8080
scm_url: https://git.osuv.de
api_token: 123abc
user: ma
key: markus@dell
expire: +5h
cert_file: ~/.ssh/test-cert.pub
gitlab:
scm_url: https://gitlab.com
api_token: ...
user: ec2-user
key: rsa@aws
expire: +1h
my_company:
server: https://hausschrat.mycompany.tld
scm_url: https://gitlab.mycompany.tld
api_token: ...
user: some_user
All parameters which are not set in addition profiles will be taken from the default profile.
In the upper my_company profile example, the values of expire and cert_file are taken from the default profile.
Metadata
Release files for hausschrat 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 | Actions |
|---|---|---|---|---|
| hausschrat-1.tar.gz | 2.5 kB | Without provenance | Details for hausschrat-1.tar.gz |
Release files / hausschrat-1.tar.gz
| Download URL | hausschrat-1.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9077760b79b6df4f03c557a0e97b48984867bb258f6a77ddff78d7c765fb1ff
|
|
BLAKE2b-256 checksum How to use checksums |
c24c3e50e3f9ae86bbefcc74dc5530c5a33d01f6f9997a70a11f048c9639f3dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.8.6
|
Security for hausschrat 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.