add projects/ - standalone scripts alongside the Docker stacks
Two real, working scripts: an Ansible playbook run-menu (the same pattern used identically across both the fleet-config and infra- provisioning repos), and cuesplit, a frame-accurate FLAC/.cue splitting utility. Sanitized paths only, logic untouched. README gets a new "Scripts & Tooling" section pointing at it, placed right after "What's Running" alongside the other repo-structure pointer.
This commit is contained in:
7 files changed
+348
No files matched your search
@@ -116,6 +116,15 @@ Authentik, self-hosted, fronts single sign-on fleet-wide — native OIDC where a
|
||||
|
||||
---
|
||||
|
||||
## Scripts & Tooling
|
||||
|
||||
A few standalone scripts live in [`projects/`](projects/) alongside the Docker stacks — real tooling, not demo code:
|
||||
|
||||
- **Ansible run-menu** — an interactive playbook runner, the same pattern used identically across both the fleet-config and infra-provisioning repos, so running anything doesn't mean remembering exact flags.
|
||||
- **cuesplit** — a small FLAC-splitting utility, frame-accurate against a .cue sheet.
|
||||
|
||||
---
|
||||
|
||||
## 👀 What I Have Explored
|
||||
I use my homelab as a real-world playground to deepen my understanding of core IT concepts. Some of the areas I've learned and put into practice are:
|
||||
|
||||
|
||||
Reference in new issue
Block a user