dotconfig
A single configuration file for .bash_profile and .gitconfig.
$ pipx install nr.dotconfig
$ dotconfig dotconfig.yaml -u
Writing /home/me/.bash_profile
Writing /home/me/.gitconfig
Example
My own dotconfig can be found here. An further example below shows how another config file can be taken as a basis for another (eg. to add work related settings on top of a personal configuration).
base: https://git.niklasrosenstein.com/NiklasRosenstein/dotconfig-files/raw/branch/master/dotconfig.yaml
profile:
blocks:
work-functions: |
function do-all-my-work() {
# it's a secret
}
gitconfig:
user:
email: my-work-mail@work.com
signingkey: WORKSIGNINKEYID
Profile.user: '{{base.gitconfig.user}}'
Copyright 2020 © Niklas Rosenstein
Metadata
Release files for nr.dotconfig 0.0.6
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 |
|---|---|---|---|---|
| nr.dotconfig-0.0.6.tar.gz | 3.7 kB | Without provenance | Details for nr.dotconfig-0.0.6.tar.gz |
Release files / nr.dotconfig-0.0.6.tar.gz
| Download URL | nr.dotconfig-0.0.6.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
984f4494f8647132658f20bfe7b2675484c23d9568666048f09aa821726ffbd1
|
|
BLAKE2b-256 checksum How to use checksums |
81f6b9b80de3508904dccdedb8f33b368e8fd9db922bd88696484568151461a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.7.5
|
Security for nr.dotconfig 0.0.6
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.