メニュー
Handle Book Corners deployment, hosting, production logs, infrastructure, and environment configuration. Use for Dokku, VPS, DNS, SSL, Grafana Loki, production debugging, deploys, rollbacks, backups, or operational commands.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Apply Book Corners Django/PostGIS domain knowledge. Use when changing models, migrations, queries, admin behavior, seed data, fixtures, geospatial behavior, slug generation, dependencies, or core library/user app architecture.
Run Book Corners local development commands. Use when starting services, running tests, applying migrations, building CSS, running the dev server, seeding demo data, or building local docs.
Handle Book Corners website UI work and validation. Use when changing Django templates, views, forms, JavaScript, HTMX interactions, static assets, CSS/Tailwind, browser behavior, or user-facing website text.
Create a GitHub issue/ticket for the Book Corners backend/web repo. Use whenever the user wants to file a bug, create a ticket, open an issue, report a problem, or request a feature/enhancement/documentation change for andreagrandi/book-corners.
Update Book Corners API behavior and documentation. Use when changing API endpoints, API schemas, API URL routing, search behavior used by the API, OpenAPI output, or API-facing request/response shapes.
Create Book Corners GitHub issues and add them to the Book Corners GitHub Project. Use when the user asks to add a ticket, create an issue, file a bug, or record an enhancement/documentation work item for this repository.
| name | book-corners-ops-workflow |
| description | Handle Book Corners deployment, hosting, production logs, infrastructure, and environment configuration. Use for Dokku, VPS, DNS, SSL, Grafana Loki, production debugging, deploys, rollbacks, backups, or operational commands. |
Use this workflow for deployment, hosting, infrastructure, production logging, and environment configuration.
Before making assumptions about production, hosting, or operational commands, consult:
README.md: project overview, local setup, management commands, and tech stack.HOSTING.md: VPS setup, DNS, SSL, environment variables, and external services.DEPLOYMENT.md: CI/CD, manual deploy, rollback, backups, Dockerfile, and troubleshooting.Production logs are shipped to Grafana Cloud Loki via Dokku Vector.
Use app="book-corners" as the default stream selector. Legacy examples using source="book-corners" may still return older entries, but new queries should use app.
Grafana Explore datasource:
grafanacloud-andreagrandi-logs
Preferred Grafana UI flow:
grafanacloud-andreagrandi-logs.app = book-corners.Recent app logs:
logcli query '{app="book-corners"}' --since 24h --limit 50
Errors only:
logcli query '{app="book-corners"} | json | level="error"' --since 24h --limit 50
Search for text:
logcli query '{app="book-corners"} |= "search term"' --since 24h --limit 50
Tail logs live:
logcli query '{app="book-corners"}' --tail
Ignore common bot noise:
logcli query '{app="book-corners"} != "wp-admin/setup-config.php" != "wordpress/wp-admin/setup-config.php"' --since 24h --limit 50
LogCLI requires LOKI_ADDR, LOKI_USERNAME, and LOKI_PASSWORD.
After Loki setup or reconfiguration, verify Vector health:
sudo dokku logs:report book-corners
sudo dokku logs:vector-logs 2>&1 | tail -80
If logs stop after reconfiguration, rerun scripts/setup_loki.sh from HOSTING.md. The script validates token auth with a direct Loki push and expects HTTP 204 before applying Dokku config.