Skip to content

Clean remaining Fly references in plugin docs #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Obsecurus merged 1 commit into from
Feb 12, 2026
Merged

Clean remaining Fly references in plugin docs #15

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions plugins/yappybara-family-kit/commands/yappybara-deploy-queue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: Inspect recent parent deploy requests saved from the Yappybara app
allowed-tools: Bash(make:*), Bash(tail:*), Bash(cat:*), Read
allowed-tools: Bash(tail:*), Bash(cat:*), Read
---

# Yappybara Deploy Queue
Expand All @@ -12,7 +12,7 @@ Review recent deployment requests submitted by parents from the app tab.
1. Run:

```bash
make deploy-queue
tail -n 20 interview-app/data/deploy-requests.jsonl
```

2. For each request, capture:
Expand All @@ -24,7 +24,7 @@ make deploy-queue

3. Prepare fulfillment plan:
- Domain/subdomain setup
- Fly.io app provisioning
- Hosting/app provisioning
- Payment confirmation status

4. Respond with a concise operations checklist and next action per request.
2 changes: 1 addition & 1 deletion plugins/yappybara-family-kit/skills/yappybara-parent-mode/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,4 +28,4 @@ Keep support parent-friendly and operationally practical.
2. Capture desired subdomain and any notes.
3. Save request via `/api/deploy-request`.
4. Add to fulfillment queue (local JSONL).
5. Share expected manual follow-up steps (payment + domain + Fly.io deploy).
5. Share expected manual follow-up steps (payment + domain + hosting rollout).