1.5 KiB
Runbook — Tap Gitea Prive hermes-skills
Date : 2026-06-17 | Instance : Toutes (common) | Statut : Deploye
Repo Gitea
URL clone : http://172.17.0.1:3232/bolbol/hermes-skills.git Acces LAN : http://192.168.100.33:3232/bolbol/hermes-skills
Structure skills/ :
- achats-tt : Achats Zone Sud Tunisie Telecom
- baserow : Acces Baserow interne bolbol.tn
- bifrost-llm : Routage LLM Bifrost (regles critiques)
- n8n-bolbol : Patterns n8n stack bolbol.tn
- nas-ops : Operations NAS Synology DS920+
- nyora-content : Production contenu Dr. Nexum / Nyora
taps.json deploye sur les 3 instances
{ "taps": [{ "repo": "http://172.17.0.1:3232/bolbol/hermes-skills.git", "path": "skills/" }] }
Chemin : /volume1/docker/hermes-platform//data/skills/.hub/taps.json Permissions : chown 1026:100
Pourquoi 172.17.0.1
Depuis les containers Docker, 192.168.100.33 inaccessible. 172.17.0.1 = gateway Docker bridge, accessible partout.
Pourquoi .git dans l URL
source-parser.ts (vercel-labs/skills) :
- owner/repo -> GitHub shorthand
- http://host/path.git -> clone git direct (notre cas) URL terminant par .git = type git direct, contourne GitHub completement.
Ajouter un skill
cd /tmp && git clone http://bolbol:2L2u519wgitea@172.17.0.1:3232/bolbol/hermes-skills.git mkdir -p hermes-skills/skills/ && vim hermes-skills/skills//SKILL.md cd hermes-skills && git add -A && git commit -m "feat: skill " git push http://bolbol:2L2u519wgitea@172.17.0.1:3232/bolbol/hermes-skills.git main