glow
The glow command line interface.
________ ____ _ __
/ ____/ / / __ \ | / /
/ / __/ / / / / / | /| / /
/ /_/ / /___/ /_/ /| |/ |/ /
\____/_____/\____/ |__/|__/
____________________________
__________________________________
________________________________________
📦 Installation
pip install glow-cli
You can set up configuration in ~/.glow/commands/<task>.yml
🚀 Usage
g list
🦋 Templating
Say you set up a config at "./commands/pod-shell.yml"
description: |
Entering the shell of the 1st pod that matches the keyword
command: |
kubectl exec -it $(kubectl get pods | grep { kw } | head -n 1 | awk '{print $1}') -- /bin/bash
inputs:
kw:
description: keyword to match
type: str
you can run the command with:
g ./commands/pod-shell.yml --kw "app1"
Or you can store the configuration by
g install ./commands/pod-shell.yml
Then you can run the command with:
g pod-shell --kw "app1"
Setup Configs and Secrets
Setup(CRUD) secrets
# to make secret token accessible to g command line
g secrets add SOME_TOKEN
g secrets list
g secrets remove SOME_TOKEN
Setup(CRUD) configs
g config add SOME_CONFIG "us-east-1"
g config list
g config remove SOME_CONFIG
🦙 LLM in CLI 💻
Why memorize commands when you can just ask?
Then you can try:
g llm "redub a.mp4 file with b.mp3, save to c.mp4 with fps 12"
Or you can ask other things in general:
g llm "explain btree to me"
Or with certain flavor to the robot role
g llm "explain btree to me" "you are a poet return everything in homer style"
✨ combine with other commands
Here's some good use cases to combine with other commands
g llm "shell into one of the pods: $(kubectl get pods) with keyword app1"
g llm "please summarize the commit message for $(git diff)"
g llm "can you explain the structure of this folder: $(ls -l)"
Choose other model
Use the following to choose other model
g configs add GLOW_LLM
Glow hub
Setup a hub on github to manage your glow commands. Say if the hub is at https://github.com/repo_owner/hub
Example structure of a hub:
./
├── README.md
├── glow
│ ├── README.md
│ ├── script-1.yml
│ ├── build-image.yml
│ ├── deploy-abc.yml
Setup
g secrets add GH_PATH
g configs add GLOW_HUB_OWNER repo_owner
g configs add GLOW_HUB_REPO hub
Install script
g glowhub script-1.yml
Metadata
Release files for glow-cli 0.3.7
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 |
|---|---|---|---|---|
| glow_cli-0.3.7.tar.gz | 19.3 kB | Without provenance | Details for glow_cli-0.3.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| glow_cli-0.3.7-py3-none-any.whl | Python 3 | none | any | Details for glow_cli-0.3.7-py3-none-any.whl |
Total release size: 42.0 kB
Release files / glow_cli-0.3.7.tar.gz
| Download URL | glow_cli-0.3.7.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6e546b6dace6347e1ac76499710ead4f0c29818eb846ec83ee8c94cc02c8622
|
|
BLAKE2b-256 checksum How to use checksums |
f3ce75948c11dbbae2eba8281bdd40c17a13020d38cd18fdd720e64be1d1d6a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / glow_cli-0.3.7-py3-none-any.whl
| Download URL | glow_cli-0.3.7-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11e138287e1d229e7e0b7e4c126290c195be4b309d576726b10d9c7ba2968c7e
|
|
BLAKE2b-256 checksum How to use checksums |
4f1d8edb211e51a1534521d1c5ea52cfe0e88485220b67fd71e11cf4191b7e50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for glow-cli 0.3.7
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.