Files

Jason Woltje 80c3680ccb feat: rename rails/ to tools/ and add service tool suites

Rename the `rails/` directory to `tools/` for agent discoverability —
agents frequently failed to locate helper scripts due to the non-intuitive
directory name. Add backward-compat symlink `rails/ → tools/`.

New tool suites:
- Authentik: auth-token, user-list, user-create, group-list, app-list,
  flow-list, admin-status (8 scripts)
- Coolify: team-list, project-list, service-list, service-status, deploy,
  env-set (7 scripts)
- Woodpecker: pipeline-list, pipeline-status, pipeline-trigger (3 stubs)
- GLPI: session-init, computer-list, ticket-list, ticket-create, user-list
  (6 scripts)
- Health: stack-health.sh — stack-wide connectivity check

Infrastructure:
- Shared credential loader at tools/_lib/credentials.sh
- install.sh creates symlink + chmod on tool scripts
- All ~253 rails/ path references updated across 68+ files

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-22 11:51:39 -06:00

pipeline-list.sh

feat: rename rails/ to tools/ and add service tool suites

2026-02-22 11:51:39 -06:00

pipeline-status.sh

feat: rename rails/ to tools/ and add service tool suites

2026-02-22 11:51:39 -06:00

pipeline-trigger.sh

feat: rename rails/ to tools/ and add service tool suites

2026-02-22 11:51:39 -06:00

README.md

feat: rename rails/ to tools/ and add service tool suites

2026-02-22 11:51:39 -06:00

README.md

Woodpecker CI Tool Suite

Interact with Woodpecker CI pipelines (list builds, check status, trigger builds).

Prerequisites

jq and curl installed
Woodpecker credentials in ~/src/jarvis-brain/credentials.json

Setup

A Woodpecker API token is required. To configure:

Go to Woodpecker CI → User Settings → API
Generate a personal token
Add to credentials.json:

{
  "woodpecker": {
    "url": "https://ci.mosaicstack.dev",
    "token": "YOUR_TOKEN_HERE"
  }
}

Scripts

Script	Purpose
`pipeline-list.sh`	List recent pipelines for a repo
`pipeline-status.sh`	Get status of a specific or latest pipeline
`pipeline-trigger.sh`	Trigger a new pipeline build

Common Options

-r owner/repo — Repository (auto-detected from git remote if omitted)
-f json — JSON output (default: table)
-h — Show help

API Reference

Base URL: https://ci.mosaicstack.dev
API prefix: /api/
Auth: Bearer token in Authorization header

Examples

# List recent builds
~/.config/mosaic/tools/woodpecker/pipeline-list.sh

# Check latest build status
~/.config/mosaic/tools/woodpecker/pipeline-status.sh

# Trigger a build on a specific branch
~/.config/mosaic/tools/woodpecker/pipeline-trigger.sh -b feature/my-branch