The Blunix Toolkit is a collection of Python glue-code that helps our
engineering team to uniformly collaborate on the development of the
already 100+ repositories we are maintaining inside our Github
organization.
The code is currently still undergoing rapid development but is already
distributed via PyPI.
## Installation
### System-wide
To install the `blunix-toolkit` system-wide, run:
```bash
sudo pip install blunix-toolkit
```
### User-Home
To install the `blunix-toolkit` in your user's home-directory, run:
```bash
pip install --user blunix-toolkit
```
Remember to add ~/.local/bin to your `$PATH` variable in your shell's
rc-file.
### Install in Python virtualenv
To install the `blunix-toolkit` into a Python virtualenv for contributing
to it, tun:
```bash
mkvirtualenv blunix-toolkit
setvirtualenvproject
make install
```
When the configuration file is accessed for the very first time, the
toolkit will ask you a set of questions regarding your name, email,
Github account, as well as your local development workspace layout.
Your answers will be marshaled to `~/.config/blunix/blunix.yaml`. This
is your individual Blunix engineering configuration file. Have a look at
it with:
```bash
blunix-config-edit
```
Please note, that you will need to use an
[API access token](https://github.com/settings/tokens) as your
Github password if you have enabled 2FA.
The toolkit core consists of a set of Python packages and modules around above
stated configuration file, as well as executable entry-point scripts that
leverage this API. These scripts can be found in the `bin/` directory.
In addition to this "core", it is possible to extend the local $SHELL
with some very useful environment variables and shell functions.
```bash
# Generate the shell-code
blunix-config-bash
# or automatically source it like this
source <(blunix-config-bash)
```
Take a look at your new environment. You should see all sorts of `BLUNIX_*`
variables and more.
```bash
set | grep -i blunix
```
# Getting started
Once your configuration file has been created you can run a set of useful
Github API requests, such as:
```bash
# list all repositories
blunix-gh-repos
# list all role-* repositories
blunix-gh-roles
# list all playbook-* repositories
blunix-gh-playbooks
```
You can now combine these scripts with the above shell-magic:
```bash
# Clone all role-* repositories to your $BLUNIX_ROOT_DIR_ROLES directory while
# additionally creating a virtualenv for each repo and setting the project
# directory to the repositories workspace directory.
blunix-gh-roles |\
cut -d/ -f2 |\
blunixForEach 'create=y clone=y blunixWorkon "$item"'
# Similar to the above, you can do the same with all Github playbook-* repositories.
blunix-gh-playbooks |\
cut -d/ -f2 |\
blunixForEach 'create=y clone=y blunixWorkon "$item"'
```
Metadata
Release files for blunix-toolkit 0.1.17
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 |
|---|---|---|---|---|
| blunix_toolkit-0.1.17.tar.gz | 5.7 kB | Without provenance | Details for blunix_toolkit-0.1.17.tar.gz |
Release files / blunix_toolkit-0.1.17.tar.gz
| Download URL | blunix_toolkit-0.1.17.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20325b0238461733a1d21482da093221cd0fdcfce6347714c4a8ac0825cd844e
|
|
BLAKE2b-256 checksum How to use checksums |
26ae9012d41bb905c0cd6521d34aec061abeff414b7bdacfc8920e8870661496
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for blunix-toolkit 0.1.17
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.