Compare commits

...

2 Commits

Author SHA1 Message Date
aeroreyna 02f6766e71 daily auto-sync 2026-06-30 2026-06-30 23:00:01 -04:00
aeroreyna 3c1dd6573d Track local network service improvements 2026-06-30 11:02:44 -04:00
5 changed files with 411 additions and 0 deletions
+17
View File
@@ -0,0 +1,17 @@
---
Date: 2026-06-30
Author: Hermes
Tags:
- journal
- family
- birthday
- grace
---
# 2026-06-30 Journal
## Grace birthday dinner at Hibachi
We came to Hibachi to celebrate [[Grace]]'s birthday. The photo captures a happy family moment around the hibachi table, with everyone smiling and Grace being playful for the camera. It looks like a warm, joyful birthday dinner together.
Photo saved: [[resources/family_photos/2026-06-30-grace-birthday-hibachi.jpg]]
+243
View File
@@ -0,0 +1,243 @@
---
Date: 2026-06-30
Author: Hermes
Tags:
- local-network
- infrastructure
- self-hosting
- previews
---
# Local Network Improvements
## Self-hosted quick web preview service
Potential improvement: build a self-hosted Cloudflare Tunnel / ngrok-style service for quickly sharing local websites online through the family server.
Goal: from any local machine, publish a local web app or static preview to a clean HTTPS URL without needing an external tunnel account.
## Proposed user experience
Run a command like:
```bash
publish-preview --name reyna-family --port 3000
```
Then get a public link such as:
```text
https://reyna-family.preview.reynafamily.com
```
or a path-style link:
```text
https://preview.reynafamily.com/reyna-family/
```
## Recommended architecture
Use FamReynaServer as the public relay:
Local machine running preview site
→ outbound tunnel to FamReynaServer
→ Caddy HTTPS reverse proxy
→ public subdomain under `preview.reynafamily.com`
Recommended stack options:
1. FRP / frp
- Best for a reusable family preview platform.
- Supports multiple tunnels and subdomains.
- More full-featured than a raw SSH tunnel.
2. Rathole
- Lightweight, fast, simple reverse tunnel.
- Good if the goal is dependable simple tunnels with less config.
3. SSH reverse tunnel
- Fastest to implement because SSH already works.
- Good first prototype.
- Less polished for many named previews.
## Safety features to include
- Random preview names by default.
- Optional password protection for previews.
- Auto-expire old previews after 7 or 30 days.
- Caddy-managed HTTPS.
- No direct exposure of local LAN services.
- Local machines only make outbound connections to FamReynaServer.
- Consider access logs and simple preview cleanup command.
## Related context
FamReynaServer already runs Caddy and has existing `reynafamily.com` subdomains. Candidate preview domains discussed:
- `preview.reynafamily.com`
- `tmp.reynafamily.com`
Initial recommendation: build with Caddy + FRP on FamReynaServer, with SSH reverse tunnel as the simplest prototype path.
## Other discussed services not yet implemented
These are related infrastructure/service ideas that have come up in conversation and should stay on the local-network / family-server improvement backlog.
### Podcast publishing service
Potential improvement: create a self-hosted podcast/audio publishing pipeline for family and ministry content.
Possible use cases:
- EMI teachings converted into audio-only episodes.
- Sermons or conference sessions published as podcast feeds.
- Kids nightly readings / family devotional mini-podcasts.
- Audio versions of selected YouTube or Subsplash recordings.
Possible service shape:
- Host RSS feeds and episode audio on FamReynaServer.
- Candidate subdomains: `podcast.reynafamily.com`, `podcast.emmint.com`, or `audio.reynafamily.com`.
- Generate episode metadata from transcripts: title, speaker, date, topic, language, summary, scripture references, and links back to video.
- Optionally publish to Apple Podcasts / Spotify later, but keep the source of truth self-hosted.
Related future automation:
- Drop an MP3/WAV into an inbox folder.
- Automatically normalize audio volume.
- Generate transcript and summary.
- Produce show notes.
- Add episode to RSS feed.
- Optionally create a WhatsApp/shareable link.
### Searchable media archive service
Potential improvement: build a searchable local archive for livestream recordings, teachings, transcripts, clips, and metadata.
Goal: make the video/audio archive reusable instead of only storing raw recordings.
Possible features:
- Store recordings on NAS / Jellyfin media storage.
- Generate transcripts for each teaching or event.
- Search by speaker, topic, scripture, language, date, event, or phrase.
- Link transcript segments back to video timestamps.
- Mark sections that are private or should not be published publicly.
- Support EMI content planning, YouTube publishing, podcast creation, and short clip extraction.
### AI-assisted content repurposing service
Potential improvement: create a repeatable pipeline that turns long-form services or teachings into outreach assets.
Possible outputs:
- Full YouTube description and title.
- Shorts/Reels clip suggestions.
- Captions/subtitles.
- Quote graphics.
- WhatsApp-shareable short clips.
- Podcast/audio episode.
- Written summary or devotional article.
- Translation drafts.
This connects to the EMI media outreach strategy and the livestream/video generation process.
### Open Design / local preview publishing bridge
Potential improvement: connect Open Design previews directly to the self-hosted preview service.
Goal: when Open Design creates a project, publish it automatically to a clean phone-friendly URL, for example:
```text
https://reyna-family.preview.reynafamily.com
```
or:
```text
https://preview.reynafamily.com/reyna-family/
```
This would avoid sending raw `127.0.0.1` or LAN-only preview links.
### Kids voice gateway speaker identification service
Potential improvement: add local speaker identification before or inside the kids Hermes voice gateway.
Goal: identify whether the speaker is Grace, Elias, Adolfo, Nicole, or unknown, then tailor responses safely.
Recommended approach discussed:
- Run the model on a local server, not on the ESP32.
- Enroll short voice samples for each family member.
- Use speaker embeddings, likely SpeechBrain ECAPA-TDNN as the first practical model.
- Treat speaker ID as context only, not authentication.
- Unknown or low-confidence speakers should default to child-safe responses.
### Kids ESP32 voice/image experience improvements
Potential improvement: continue improving the child-facing ESP32 assistant experience.
Possible features:
- Voice requests from kid devices routed to the separate `kids` Hermes profile.
- Short age-appropriate spoken replies.
- Image-aware interactions when a device sends a photo.
- Simple visual replies or animations on ESP32 screens.
- Parent-safe tool permissions and no admin/system tools exposed to children.
- Possible integration with local speaker identification.
### Brain MCP / local knowledge service
Potential improvement: continue the PARA brain MCP server idea so local notes can be searched, read, and eventually written through a safer structured service.
Known open questions from the brain MCP project:
- Should it be a long-lived service or launched on demand by Hermes?
- Should write access start read-only/search-only first?
- How should Git commits and pushes be automated after writes?
- How can it preserve frontmatter, Obsidian links, and PARA filing rules?
### Mac mini Voicebox voice generation service
Implemented in Reyna CLI on 2026-06-30 as `reyna-cli voicebox` and `reyna-cli macmini voicebox`.
Observed service state:
- Mac mini host: `192.168.68.102` / `Mac-mini-M4.local`.
- Voicebox app server process: `/Applications/Voicebox.app/Contents/MacOS/voicebox-server`.
- Voicebox REST API: `http://127.0.0.1:17493` on the Mac mini.
- Direct LAN access from the Pi to `http://192.168.68.102:17493` was still refused during verification, so Reyna CLI tries the LAN URL first and falls back to SSH-local access on the Mac mini.
- Verified commands: health, profiles, generate, generation lookup.
Useful commands:
```bash
reyna-cli voicebox health --json
reyna-cli voicebox profiles --json
reyna-cli voicebox generate "Hello from Reyna CLI" --profile Nicole --engine kokoro --json
reyna-cli voicebox generation <generation-id> --json
```
Potential future improvement: if Voicebox should truly be reachable directly from LAN, adjust the Voicebox server bind host or run a small localhost-only reverse proxy on the Mac mini that binds to the LAN interface with appropriate access controls.
### Local service registry / subdomain map
Potential improvement: maintain a single local service registry for family infrastructure.
Goal: reduce scattered knowledge about which services run where.
Possible contents:
- Service name.
- Host machine.
- Internal IP and port.
- Public subdomain.
- Caddy reverse proxy target.
- Auth method.
- Backup/restore notes.
- Owner / intended audience.
- Whether it is private, family-only, EMI, or public.
This would pair well with Caddy, FamReynaServer, and the brain.
Binary file not shown.

After

Width:  |  Height:  |  Size: 110 KiB

@@ -0,0 +1,49 @@
---
Date: 2026-06-30
Author: Hermes
Tags: [music, chords, worship, cache]
---
# En Tu Luz Chord Cache
## Song
- Title: En Tu Luz
- Also searched by lyric cue: “Eres nuestra herencia, más que suficiente”
- Artist: En Espíritu y En Verdad
- Key found: E
- Source checked: https://acordes.lacuerda.net/en_espiritu_y_en_verdad/en_tu_luz
- Cache PDF: [[en-tu-luz-chord-chart.pdf]]
## Copyright-safe chord chart
This cache stores a chord-only / section-outline chart rather than full lyrics.
```text
Title: En Tu Luz / Eres Nuestra Herencia
Artist: En Espíritu y En Verdad
Key: E
Tempo: worship ballad / medium slow
Intro / Verse pattern:
| E | E | C#m | A |
| E | E | C#m | A |
Pre-Chorus / Tag:
| B/D# | C#m | B | E |
| B/D# | C#m | B | A E |
Chorus:
| E | B | A C#m | B |
Suggested arrangement:
Intro x1
Verse x1
Pre-Chorus x1
Chorus x2
Instrumental: Verse pattern x1
Pre-Chorus x1
Chorus x2-4
End on E
```
## Notes
- Identified from the lyric fragment the user gave: “eres nuestra herencia, más que suficiente.”
- Use this cached PDF first on future requests unless the user asks for a different key or a full lyric/chord sheet.
@@ -0,0 +1,102 @@
%PDF-1.4
1 0 obj
<< /Type /Catalog /Pages 2 0 R >>
endobj
2 0 obj
<< /Type /Pages /Kids [3 0 R] /Count 1 >>
endobj
3 0 obj
<< /Type /Page /Parent 2 0 R /MediaBox [0 0 612 792] /Resources << /Font << /F1 4 0 R /F2 5 0 R >> >> /Contents 6 0 R >>
endobj
4 0 obj
<< /Type /Font /Subtype /Type1 /BaseFont /Helvetica >>
endobj
5 0 obj
<< /Type /Font /Subtype /Type1 /BaseFont /Courier >>
endobj
6 0 obj
<< /Length 1401 >>
stream
BT
/F1 22 Tf
72 770 Td (En Tu Luz / Eres Nuestra Herencia) Tj
-72 -770 Td
/F1 13 Tf
72 742 Td (En Espiritu y En Verdad - Key: E) Tj
-72 -742 Td
/F1 9 Tf
72 720 Td (Chord-only worship chart cached in ~/brain - Source checked: LaCuerda) Tj
-72 -720 Td
/F1 11 Tf
72 689 Td (Lyric cue: "Eres nuestra herencia, mas que suficiente") Tj
-72 -689 Td
/F1 14 Tf
72 655 Td (Intro / Verse pattern) Tj
-72 -655 Td
/F2 13 Tf
72 633 Td (| E | E | C#m | A |) Tj
-72 -633 Td
/F2 13 Tf
72 613 Td (| E | E | C#m | A |) Tj
-72 -613 Td
/F1 14 Tf
72 577 Td (Pre-Chorus / Tag) Tj
-72 -577 Td
/F2 13 Tf
72 555 Td (| B/D# | C#m | B | E |) Tj
-72 -555 Td
/F2 13 Tf
72 535 Td (| B/D# | C#m | B | A E |) Tj
-72 -535 Td
/F1 14 Tf
72 499 Td (Chorus) Tj
-72 -499 Td
/F2 13 Tf
72 477 Td (| E | B | A C#m | B |) Tj
-72 -477 Td
/F1 14 Tf
72 441 Td (Suggested arrangement) Tj
-72 -441 Td
/F2 13 Tf
72 419 Td (Intro x1) Tj
-72 -419 Td
/F2 13 Tf
72 399 Td (Verse x1) Tj
-72 -399 Td
/F2 13 Tf
72 379 Td (Pre-Chorus x1) Tj
-72 -379 Td
/F2 13 Tf
72 359 Td (Chorus x2) Tj
-72 -359 Td
/F2 13 Tf
72 339 Td (Instrumental: Verse pattern x1) Tj
-72 -339 Td
/F2 13 Tf
72 319 Td (Pre-Chorus x1) Tj
-72 -319 Td
/F2 13 Tf
72 299 Td (Chorus x2-4) Tj
-72 -299 Td
/F2 13 Tf
72 279 Td (End on E) Tj
-72 -279 Td
/F1 9 Tf
72 243 Td (Note: chord-only/section-outline chart, not a full lyric sheet.) Tj
-72 -243 Td
ET
endstream
endobj
xref
0 7
0000000000 65535 f
0000000009 00000 n
0000000058 00000 n
0000000115 00000 n
0000000251 00000 n
0000000321 00000 n
0000000389 00000 n
trailer << /Size 7 /Root 1 0 R >>
startxref
1842
%%EOF