Skip to content
Closed
Show file tree
Hide file tree
Changes from 3 commits
Commits
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
22 changes: 20 additions & 2 deletions .coderabbit.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -16,5 +16,23 @@ reviews:
- "main"
- "origin/main"

# Language setting (locale for reviews)
language: "en"
# Documentation comment requirements
documentation:
# Require docstrings for Python functions/classes
coverage:
minimum: 80
patch: 80

# Language-specific settings
language: "python"

# Review depth settings
review:
# Number of commits to review in a PR
num_commits: 10

# Include summary of PR
summary: true

# Enable line-by-line reviews
Comment on lines +20 to +35

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# Find and read the .coderabbit.yaml file
find . -name ".coderabbit.yaml" -o -name "coderabbit.yaml" | head -20

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 85


🏁 Script executed:

# Also search for schema-related files
find . -type f \( -name "*schema*" -o -name "*config*" \) | grep -E "\.(json|yaml|yml)$" | head -20

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 244


🏁 Script executed:

# Look for documentation files that might describe the schema
find . -type f \( -name "*.md" -o -name "*.rst" \) | xargs grep -l "coderabbit\|CodeRabbit\|schema" 2>/dev/null | head -10

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 445


🏁 Script executed:

# Read the .coderabbit.yaml file with line numbers
cat -n ./.coderabbit.yaml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 1106


🌐 Web query:

CodeRabbit .coderabbit.yaml schema configuration documentation

💡 Result:

Here are the official CodeRabbit docs for the .coderabbit.yaml schema and configuration:

  • Configuration reference (full schema-driven field list & descriptions). [1]
  • Guide: configuring CodeRabbit via a .coderabbit.yaml file with examples and template. [2]
  • Notes on configuration inheritance and hierarchy (how repository/central/UI settings merge). [3]

Key points: place .coderabbit.yaml in the repository root; the docs include example files and the machine-readable JSON schema (referenced in examples as yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json). [2][1]

Sources:

  1. CodeRabbit — Configuration reference. [1]
  2. CodeRabbit — Configure using a YAML file (examples & template). [2]
  3. CodeRabbit — Configuration inheritance (hierarchy & merging). [3]

🌐 Web query:

CodeRabbit schema json https://coderabbit.ai/integrations/schema.v2.json documentation review top-level keys

💡 Result:

Top-level keys in the CodeRabbit schema (schema.v2.json) and brief descriptions:

  • language — locale for reviews (ISO codes, default "en-US"). [1]
  • tone_instructions — custom tone for reviews/chat (string). [1]
  • early_access — enable early-access features (boolean). [1]
  • enable_free_tier — enable free-tier features (boolean). [1]
  • inheritance — whether to inherit parent settings (boolean). [1]
  • reviews — object with many review-related settings (profile, summaries, labeling, auto-review, path filters, commit/review status, etc.). [1]
  • finishing_touches — options for generated docstrings and unit tests. [1]
  • pre_merge_checks — pre-merge check configuration (docstring coverage, title/description checks, linked-issue assessment, custom checks). [1]

Source: CodeRabbit schema JSON. [1] https://coderabbit.ai/integrations/schema.v2.json


🌐 Web query:

CodeRabbit configuration pre_merge_checks docstrings threshold

💡 Result:

Short answer: CodeRabbit’s pre_merge_checks include a Docstring Coverage check with a configurable "threshold" (percentage). The default threshold is 80% and you can set it in .coderabbit.yaml under reviews.pre_merge_checks.docstrings.threshold (example: threshold: 85). You can also set the check’s mode (off | warning | error). [1][2]

Sources:

  • CodeRabbit Pre‑Merge Checks (Docstring Coverage, default 80% and YAML example). [1]
  • Configuration reference / .coderabbit.yaml schema (pre_merge_checks.docstrings). [2]

documentation and review are invalid top-level keys in CodeRabbit schema.

Per the official CodeRabbit schema (schema.v2.json), valid top-level keys are reviews, pre_merge_checks, language, tone_instructions, early_access, enable_free_tier, inheritance, and finishing_touches. The documentation and review blocks at lines 20–36 will be ignored.

Move documentation coverage to pre_merge_checks.docstrings.threshold and keep review settings nested within the reviews block:

🔧 Schema-aligned adjustment
 reviews:
   review_status: true
   branches:
     - "PMOVES.AI-Edition-Hardened"
     - "PMOVES.AI-Edition-Hardened-v3-clean"
     - "feat/hardened-*"
     - "fix/hardened-*"
   excluded_branches:
     - "main"
     - "origin/main"
+  num_commits: 10
+  summary: true
+  line_comments: true
 
-# Documentation comment requirements
-documentation:
-  # Require docstrings for Python functions/classes
-  coverage:
-    minimum: 80
-    patch: 80
-
-# Review depth settings
-review:
-  # Number of commits to review in a PR
-  num_commits: 10
-
-  # Include summary of PR
-  summary: true
-
-  # Enable line-by-line reviews
-  line_comments: true
+
+pre_merge_checks:
+  docstrings:
+    threshold: 80
🤖 Prompt for AI Agents
In @.coderabbit.yaml around lines 20 - 35, The config uses invalid top-level
keys "documentation" and "review"; move the docstring coverage settings into
pre_merge_checks.docstrings.threshold (set to 80 from coverage.minimum/patch)
and relocate the review settings under a top-level "reviews" block, e.g., copy
review.num_commits -> reviews.num_commits, review.summary -> reviews.summary,
and enable the line-by-line flag as reviews.line_by_line (true) so the schema
matches schema.v2.json and those settings are honored.

line_comments: true
2 changes: 1 addition & 1 deletion .github/workflows/chit-contract.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ permissions:

jobs:
verify:
runs-on: [self-hosted, vps]
runs-on: ubuntu-latest
steps:
- name: Harden Runner
uses: step-security/harden-runner@v2
Expand Down
2 changes: 1 addition & 1 deletion pmoves/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -1427,7 +1427,7 @@ up-jellyfin-single: ## Single Jellyfin using your forked image (8096)
@$(MAKE) --no-print-directory down-jellyfin-ai
@docker network create cataclysm-net >/dev/null 2>&1 || true
@bash -lc '$(LOAD_ENV_SHARED) files="-f docker-compose.external.yml"; if [ -f docker-compose.jellyfin.hosts.yml ]; then files="$$files -f docker-compose.jellyfin.hosts.yml"; fi; exec docker compose -p $(PROJECT) $$files up -d --pull $(PULL) jellyfin-ext'
@echo "✔ Jellyfin (single) up at http://localhost:8096 using $${JELLYFIN_IMAGE:-ghcr.io/cataclysm-studios-inc/pmoves-jellyfin:pmoves-latest}"
@echo "✔ Jellyfin (single) up at http://localhost:8096 using $${JELLYFIN_IMAGE:-ghcr.io/powerfulmoves/pmoves-jellyfin:pmoves-latest}"

.PHONY: jellyfin-enhanced-smoke
jellyfin-enhanced-smoke: ## Validate Jellyfin core (/System/Info, /Plugins) and web assets on single instance
Expand Down
27 changes: 22 additions & 5 deletions pmoves/docker-compose.external.yml
Original file line number Diff line number Diff line change
@@ -1,9 +1,26 @@
# YAML anchors for tier-based env file loading
# These reference the tier env files from parent docker-compose.yml
x-env-tier-data: &env-tier-data
env_file:
- path: env.tier-data
required: false

x-env-tier-worker: &env-tier-worker
env_file:
- path: env.tier-worker
required: false

x-env-tier-media: &env-tier-media
env_file:
- path: env.tier-media
required: false

services:
wger:
image: ${WGER_IMAGE:-ghcr.io/powerfulmoves/pmoves-health-wger:pmoves-latest}
container_name: cataclysm-wger
restart: unless-stopped
env_file: [env.shared.generated, env.shared, .env.generated, .env.local]
<<: *env-tier-worker
networks:
cataclysm:
aliases:
Expand Down Expand Up @@ -42,7 +59,7 @@ services:
image: ${FIREFLY_IMAGE:-ghcr.io/powerfulmoves/pmoves-wealth:pmoves-latest}
container_name: cataclysm-firefly
restart: unless-stopped
env_file: [env.shared.generated, env.shared, .env.generated, .env.local]
<<: *env-tier-worker
networks:
cataclysm:
aliases:
Expand All @@ -65,7 +82,7 @@ services:
open-notebook-surrealdb-ext:
image: ${OPEN_NOTEBOOK_SURREAL_IMAGE:-surrealdb/surrealdb:v2}
container_name: cataclysm-open-notebook-surrealdb
env_file: [env.shared.generated, env.shared, .env.generated, .env.local]
<<: *env-tier-data
command: start --log info --user ${SURREAL_USER} --pass ${SURREAL_PASS} rocksdb:/mydata/mydatabase.db
restart: unless-stopped
user: "0:0"
Expand All @@ -82,7 +99,7 @@ services:
# Default to the Open Notebook fork; override OPEN_NOTEBOOK_IMAGE to pin your own tag.
container_name: cataclysm-open-notebook
restart: unless-stopped
env_file: [env.shared.generated, env.shared, .env.generated, .env.local]
<<: *env-tier-worker
depends_on:
- open-notebook-surrealdb-ext
networks:
Expand All @@ -105,7 +122,7 @@ services:
image: ${JELLYFIN_IMAGE:-ghcr.io/powerfulmoves/pmoves-jellyfin:pmoves-latest}
container_name: cataclysm-jellyfin
restart: unless-stopped
env_file: [env.shared.generated, env.shared, .env.generated, .env.local]
<<: *env-tier-media
networks:
cataclysm:
aliases:
Expand Down
2 changes: 1 addition & 1 deletion pmoves/docker-compose.gpu-image.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
hi-rag-gateway-v2-gpu:
image: ${HIRAG_V2_GPU_IMAGE:-ghcr.io/cataclysm-studios-inc/hi-rag-gateway-v2-gpu:cu128-py310-stable}
image: ${HIRAG_V2_GPU_IMAGE:-ghcr.io/powerfulmoves/hi-rag-gateway-v2-gpu:cu128-py310-stable}
runtime: nvidia
Comment on lines 2 to 4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# Search for references to this image in the codebase
rg "hi-rag-gateway-v2-gpu" --type yml --type yaml -A 2 -B 2

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 94


🏁 Script executed:

# Look for any CI/CD, build, or deployment files that might reference image publishing
fd -e "yml" -e "yaml" -e "json" -e "dockerfile" -e "Dockerfile" | head -20

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 929


🏁 Script executed:

# Check the docker-compose file structure and any environment variable documentation
cat pmoves/docker-compose.gpu-image.yml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 2208


🏁 Script executed:

# Search for any documentation or scripts related to GPU image building/publishing
fd -e "md" -e "sh" -e "py" | xargs rg -l "HIRAG.*GPU|cu128|py310" 2>/dev/null | head -10

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 348


🏁 Script executed:

# Check the hi-rag-gateway-v2 documentation
cat pmoves/docs/services/hi-rag-gateway-v2/README.md | head -100

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 6272


🏁 Script executed:

# Search for GitHub Actions or CI/CD workflows
fd -e "yml" -e "yaml" | xargs rg -l "ghcr.io|gpu|image" | grep -i "workflow\|action\|ci\|\.github"

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Look for any GitHub Actions workflows
fd ".github" -type d

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 237


🏁 Script executed:

# Search for Dockerfile related to hi-rag-gateway-v2-gpu
fd -i "dockerfile*" | xargs grep -l "hi-rag-gateway\|cu128\|py310" 2>/dev/null

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 295


🏁 Script executed:

# Search for any image build or publish scripts
rg "ghcr.io/powerfulmoves/hi-rag-gateway-v2-gpu" --type-list all -l

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 456


🏁 Script executed:

# Check the Dockerfile.gpu to see what organization it references
cat pmoves/services/hi-rag-gateway-v2/Dockerfile.gpu

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 2244


🏁 Script executed:

# Search for references to both organizations in the codebase
rg "cataclysm-studios-inc|powerfulmoves" --type yaml -B 2 -A 2

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 6580


🏁 Script executed:

# Look for any CI/CD workflows or build scripts that push images
fd -type f -name "*.yml" -o -name "*.yaml" | xargs grep -l "push\|build\|registry\|ghcr" 2>/dev/null | head -10

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 237


🏁 Script executed:

# Check if there are any recent commits or documentation about the image registry
rg "HIRAG_V2_GPU_IMAGE" -B 2 -A 2

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 1412


Clarify the correct GHCR organization for the GPU image.

The docker-compose file specifies ghcr.io/powerfulmoves/hi-rag-gateway-v2-gpu:cu128-py310-stable, but the service documentation recommends ghcr.io/cataclysm-studios-inc/hi-rag-gateway-v2-gpu:cu128-py310-stable. Verify which organization hosts the actual image and update either the compose file or documentation to ensure the tag is correct, or the container will fail to pull at startup.

🤖 Prompt for AI Agents
In `@pmoves/docker-compose.gpu-image.yml` around lines 2 - 4, The docker-compose
entry for service hi-rag-gateway-v2-gpu references an incorrect GHCR
organization in the image value (image:
${HIRAG_V2_GPU_IMAGE:-ghcr.io/powerfulmoves/hi-rag-gateway-v2-gpu:cu128-py310-stable});
verify which org actually hosts the image (powerfulmoves vs
cataclysm-studios-inc) and update the default image tag or the docs to the
correct registry string so pulls succeed; change the fallback value in the
HIRAG_V2_GPU_IMAGE default to
ghcr.io/cataclysm-studios-inc/hi-rag-gateway-v2-gpu:cu128-py310-stable if that
is the correct host (or update docs to match the powerfulmoves org) and add a
brief comment clarifying the authoritative source.

restart: unless-stopped
env_file: [env.shared.generated, env.shared, .env.generated, .env.local]
Expand Down
8 changes: 4 additions & 4 deletions pmoves/env.shared.example
Original file line number Diff line number Diff line change
Expand Up @@ -134,9 +134,9 @@ SENTENCE_MODEL=all-MiniLM-L6-v2
# ---- Agent UI images (published) ----
# Override to use published images for headless+UI builds instead of building locally.
# Example stable tags (adjust as your registry publishes):
AGENT_ZERO_IMAGE=ghcr.io/cataclysm-studios-inc/pmoves-agent-zero:2025.12.13
ARCHON_IMAGE=ghcr.io/cataclysm-studios-inc/pmoves-archon:2025.12.13
ARCHON_UI_IMAGE=ghcr.io/cataclysm-studios-inc/pmoves-archon-ui:2025.12.13
AGENT_ZERO_IMAGE=ghcr.io/powerfulmoves/pmoves-agent-zero:2025.12.13
ARCHON_IMAGE=ghcr.io/powerfulmoves/pmoves-archon:2025.12.13
ARCHON_UI_IMAGE=ghcr.io/powerfulmoves/pmoves-archon-ui:2025.12.13
DEEPRESEARCH_IMAGE=ghcr.io/powerfulmoves/pmoves-deepresearch:stable
SUPASERCH_IMAGE=ghcr.io/powerfulmoves/pmoves-supaserch:stable

Expand Down Expand Up @@ -171,7 +171,7 @@ SINGLE_USER_MODE=1
NEXT_PUBLIC_SINGLE_USER_MODE=1

# PMOVES.YT (optional published image)
PMOVES_YT_IMAGE=ghcr.io/cataclysm-studios-inc/pmoves-yt:2025.12.13
PMOVES_YT_IMAGE=ghcr.io/powerfulmoves/pmoves-yt:2025.12.13

## Open Notebook
# Knowledge management system using SurrealDB backend
Expand Down
20 changes: 14 additions & 6 deletions pmoves/env.tier-agent
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
# =============================================================================
# PMOVES Agent Tier Environment Variables
# Services: agent-zero, archon, mesh-agent, supaserch, deepresearch,
# consciousness-service, archon-agent-work-orders, botz-gateway,
# publisher-discord, messaging-gateway, jellyfin-bridge, chat-relay
# =============================================================================
# publisher-discord, messaging-gateway, jellyfin-bridge, chat-relay,
# github-runner-ctl

# Agent tier services handle orchestration and coordination
# They connect to internal services (Hi-RAG, NATS, Supabase)
Expand All @@ -17,9 +16,9 @@ NATS_URL=nats://nats:4222
# ---------------------------------------------------------------------------
# Supabase (internal)
# ---------------------------------------------------------------------------
SUPABASE_URL=http://postgrest:3000
SUPABASE_URL=http://supabase_kong_PMOVES.AI:8000
SUPABASE_SERVICE_ROLE_KEY= # REQUIRED: From Supabase CLI
SUPA_REST_URL=http://postgrest:3000/rest/v1
SUPA_REST_URL=http://supabase_kong_PMOVES.AI:8000/rest/v1
Comment on lines +19 to +21

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for docker-compose files and check for container name patterns
find . -type f \( -name "docker-compose*" -o -name "*.compose.yml" -o -name "*.compose.yaml" \) | head -20

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 639


🏁 Script executed:

# Search for supabase_kong container references in compose files
rg -n "supabase_kong" -A 2 -B 2 --type yaml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 2111


🏁 Script executed:

# Also check for any references to the specific container name with dots
rg -n "supabase_kong_PMOVES\.AI" --type yaml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 666


🏁 Script executed:

# Search for service definitions in docker-compose files - look for supabase services
rg -n "services:" -A 300 pmoves/docker-compose.yml | grep -A 50 "supabase"

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 3983


🏁 Script executed:

# Look for the supabase_kong service definition more specifically
rg -n "supabase_kong" -B 5 -A 5 pmoves/docker-compose.yml | head -50

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 1740


🏁 Script executed:

# Check if there's a network definition that might explain the naming
rg -n "networks:" -A 20 pmoves/docker-compose.yml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 42643


🏁 Script executed:

# Search for any service definition named supabase_kong
rg -n "supabase_kong:" pmoves/docker-compose.yml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Look for container_name or hostname definitions that might set this name
rg -n "container_name|hostname" pmoves/docker-compose.yml | grep -i supabase

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Search across all compose files for supabase_kong service definition
find pmoves -name "docker-compose*.yml" -exec rg -l "supabase_kong:" {} \;

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Search for supabase_kong in all files and directories
find pmoves -type f \( -name "*.yml" -o -name "*.yaml" -o -name "*.env*" \) -exec rg -l "supabase_kong" {} \;

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 128


🏁 Script executed:

# Check if there's a separate supabase compose or configuration directory
ls -la pmoves/ | grep -i supabase

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 127


🏁 Script executed:

# Search for any references that might explain this configuration
rg -n "supabase_kong_PMOVES\.AI" --type yaml --type txt

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 666


🏁 Script executed:

# Check contents of supabase directory
ls -la pmoves/supabase/

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 351


🏁 Script executed:

# Look for any service definition or configuration in supabase directory
find pmoves/supabase -type f \( -name "*.yml" -o -name "*.yaml" -o -name "*.json" -o -name "docker-compose*" \) | head -20

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Check if there's documentation or README about the supabase setup
find pmoves/supabase -name "README*" -o -name "*.md" | xargs cat 2>/dev/null

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Check if postgrest service uses container_name or aliases that might explain the supabase_kong name
rg -n "postgrest" -B 5 -A 20 pmoves/docker-compose.yml | grep -A 20 "^postgrest:"

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Look for any network alias definitions that might create this hostname
rg -n "aliases:" -A 5 pmoves/docker-compose.yml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 217


🏁 Script executed:

# Check the env file referenced in the review to see if there's more context
cat -n pmoves/env.tier-agent | head -30

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 1705


🏁 Script executed:

# Check if there's any documentation about supabase setup or external service
find pmoves -name "*.md" -o -name "README*" | xargs grep -l "supabase_kong\|Kong\|gateway" 2>/dev/null | head -5

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 384


🏁 Script executed:

# Look for any instructions about external Supabase setup
find . -maxdepth 2 -name "*.md" | xargs grep -l "Supabase\|supabase" 2>/dev/null

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 518


🏁 Script executed:

# Verify the complete context of postgrest service definition
rg -n "postgrest:" -A 30 pmoves/docker-compose.yml | head -50

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 1776


🏁 Script executed:

# Search for any Kong service or gateway configuration
rg -n "kong" -i pmoves/docker-compose.yml

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 421


🏁 Script executed:

# Check if there's documentation about external Supabase or Kong setup
cat ./README.md | grep -A 10 -B 2 -i "supabase\|kong" | head -40

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 5412


🏁 Script executed:

# Look for any env file that might have the actual service definition
find pmoves -name "env*" -type f | xargs grep -l "supabase_kong" 2>/dev/null

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 118


🏁 Script executed:

# Check the Supabase service documentation
cat pmoves/docs/services/supabase/README.md 2>/dev/null | head -100

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Check the env example file to see if there's guidance
cat pmoves/env.tier-agent.example | head -30

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 1577


🏁 Script executed:

# Check if there's documentation about Supabase CLI setup
grep -r "supabase start\|supabase_kong\|Kong gateway" pmoves/docs/ 2>/dev/null | head -20

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 2018


🏁 Script executed:

# Look at the main README for Supabase setup instructions
cat pmoves/README.md 2>/dev/null | grep -A 20 -B 5 -i "supabase\|kong" | head -60

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 49


🏁 Script executed:

# Check the LOCAL_TOOLING_REFERENCE mentioned in main README
cat pmoves/docs/LOCAL_TOOLING_REFERENCE.md 2>/dev/null | grep -A 10 -B 2 -i "supabase\|kong\|port 8000" | head -50

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 9863


🏁 Script executed:

# Verify the correct Supabase internal hostname from documentation
cat pmoves/docs/LOCAL_TOOLING_REFERENCE.md | grep -A 5 -B 5 "api.supabase.internal"

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 2585


🏁 Script executed:

# Check if there are any recent changes or PRs related to supabase_kong
git log --oneline -20 -- pmoves/env.tier-agent pmoves/docker-compose.yml 2>/dev/null | head -10

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 149


🏁 Script executed:

# Verify what the actual Supabase CLI provides
grep -r "api.supabase\|supabase.internal" pmoves/docs/ pmoves/*.md 2>/dev/null

Repository: POWERFULMOVES/PMOVES.AI

Length of output: 2033


Correct the Supabase URL hostname to match the documented standard.

The hostname supabase_kong_PMOVES.AI does not exist in the docker-compose configuration. According to the documentation (LOCAL_TOOLING_REFERENCE.md, Dec 2025), services targeting the Supabase stack should use http://api.supabase.internal:8000 instead. Update lines 19 and 21 to:

SUPABASE_URL=http://api.supabase.internal:8000
SUPA_REST_URL=http://api.supabase.internal:8000/rest/v1

This matches the established pattern for compose-based Supabase networking and will resolve DNS correctly inside Docker containers on the pmoves-net network.

🤖 Prompt for AI Agents
In `@pmoves/env.tier-agent` around lines 19 - 21, Replace the non-existent
hostname in the environment variables by updating SUPABASE_URL and SUPA_REST_URL
to use the documented internal Supabase host; specifically change the values
assigned to SUPABASE_URL and SUPA_REST_URL from
http://supabase_kong_PMOVES.AI:8000 and
http://supabase_kong_PMOVES.AI:8000/rest/v1 to use
http://api.supabase.internal:8000 and http://api.supabase.internal:8000/rest/v1
respectively so containers on the pmoves-net can resolve the Supabase service.


# ---------------------------------------------------------------------------
# Hi-RAG Gateway (internal)
Expand Down Expand Up @@ -50,7 +49,7 @@ AGENTZERO_JETSTREAM=true
# ---------------------------------------------------------------------------
ARCHON_SERVER_PORT=8091
ARCHON_MCP_PORT=8051
ARCHON_SUPABASE_BASE_URL=http://postgrest:3000
ARCHON_SUPABASE_BASE_URL=http://supabase_kong_PMOVES.AI:8000

# ---------------------------------------------------------------------------
# DeepResearch Settings
Expand All @@ -65,3 +64,12 @@ DEEPRESEARCH_NOTEBOOK_EMBED=true
# ---------------------------------------------------------------------------
DISCORD_WEBHOOK_URL= # Optional: Discord webhook for notifications

# ---------------------------------------------------------------------------
# GitHub Runner Controller (CI/CD orchestration)
# ---------------------------------------------------------------------------
GITHUB_RUNNER_CTL_PORT=8100
GITHUB_RUNNER_CTL_WEB_PORT=8104
GITHUB_RUNNER_CTL_LOG_LEVEL=INFO
GITHUB_REPOSITORIES=POWERFULMOVES/PMOVES.AI
GITHUB_RUNNER_REFRESH_INTERVAL=60

25 changes: 17 additions & 8 deletions pmoves/env.tier-api
Original file line number Diff line number Diff line change
Expand Up @@ -9,24 +9,25 @@

# PostgreSQL Connection (for PostgREST)
POSTGRES_USER=pmoves
# REQUIRED: Must match env.tier-data POSTGRES_PASSWORD
POSTGRES_PASSWORD=A7sX9kL2mN4pQ8rT6vW3yZ5bC1dE8fG0hJ2
# REQUIRED: Generate with `openssl rand -base64 24` for production deployments
POSTGRES_PASSWORD=
POSTGRES_DB=pmoves
PGRST_DB_SCHEMA=public,pmoves_core
PGRST_DB_ANON_ROLE=anon
PGRST_SERVER_PORT=3000
# REQUIRED: Generate with `openssl rand -base64 32`
SUPABASE_JWT_SECRET=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJwbW92ZXMtYXBpIn0.fake_jwt_secret_replace_with_real
# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
SUPABASE_JWT_SECRET=

# MinIO Connection (for Presign)
MINIO_ENDPOINT=minio:9000
# REQUIRED: Must match env.tier-data MINIO credentials
# REQUIRED: Set unique access key for production deployments
MINIO_ACCESS_KEY=
# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
MINIO_SECRET_KEY=
MINIO_SECURE=false
AWS_DEFAULT_REGION=us-east-1
ALLOWED_BUCKETS=assets,outputs
# REQUIRED: Generate with `openssl rand -hex 32`
# REQUIRED: Generate with `openssl rand -hex 32` for production deployments
PRESIGN_SHARED_SECRET=

# Hi-RAG Gateway (for retrieval-eval)
Expand All @@ -38,5 +39,13 @@ QDRANT_URL=http://qdrant:6333
QDRANT_COLLECTION=pmoves_chunks_qwen3

# Meilisearch Connection (for Hi-RAG)
# REQUIRED: Must match env.tier-data MEILI_MASTER_KEY
MEILI_MASTER_KEY=JOoQIIAp9sedrTMd0XXL6cdtTRpUYlmh
# REQUIRED: Generate with `openssl rand -hex 32` for production deployments
MEILI_MASTER_KEY=

# Neo4j Connection (for Hi-RAG Knowledge Graph)
NEO4J_URI=bolt://neo4j:7687
NEO4J_USER=neo4j
# REQUIRED: Generate with `openssl rand -base64 24` for production deployments
NEO4J_PASSWORD=
# REQUIRED: Generate with `openssl rand -base64 24` for production deployments (format: neo4j/password)
NEO4J_AUTH=
17 changes: 10 additions & 7 deletions pmoves/env.tier-data
Original file line number Diff line number Diff line change
Expand Up @@ -4,28 +4,31 @@
# Services: postgres, qdrant, neo4j, meilisearch, minio, nats
# Scope: Infrastructure credentials ONLY (no external API keys)
#
# Copy to `env.tier-data` and fill in real values. The file is gitignored.
# Fill in real values below. This file is gitignored.
# =============================================================================

# PostgreSQL (pgvector)
# Used by: postgres service, all services that query Supabase/PostgREST
POSTGRES_DB=pmoves
POSTGRES_USER=pmoves
# REQUIRED: Generate with `openssl rand -base64 24`
POSTGRES_PASSWORD=A7sX9kL2mN4pQ8rT6vW3yZ5bC1dE8fG0hJ2
# REQUIRED: Generate with `openssl rand -base64 24` for production deployments
# For development, a safe default is provided
POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-pmoves_dev}
Comment on lines +14 to +16

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Shell variable expansion won't work in Docker Compose env_file.

Docker Compose's env_file directive reads files as literal key=value pairs without shell expansion. The syntax ${POSTGRES_PASSWORD:-pmoves_dev} will be passed as a literal string, not expanded to pmoves_dev.

🐛 Proposed fix

For dev defaults, either:

Option 1: Use literal default value (recommended for dev env file):

-POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-pmoves_dev}
+POSTGRES_PASSWORD=pmoves_dev

Option 2: Leave empty and set defaults in docker-compose.yml environment section:

environment:
  POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-pmoves_dev}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# REQUIRED: Generate with `openssl rand -base64 24` for production deployments
# For development, a safe default is provided
POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-pmoves_dev}
# REQUIRED: Generate with `openssl rand -base64 24` for production deployments
# For development, a safe default is provided
POSTGRES_PASSWORD=pmoves_dev
🤖 Prompt for AI Agents
In `@pmoves/env.tier-data` around lines 14 - 16, The env file uses shell-style
expansion which Docker Compose does not perform, so change the POSTGRES_PASSWORD
entry in env.tier-data to a literal value (e.g., POSTGRES_PASSWORD=pmoves_dev)
for dev, or leave POSTGRES_PASSWORD blank in env.tier-data and move the
defaulting logic into your docker-compose.yml environment section using the
${POSTGRES_PASSWORD:-pmoves_dev} expansion; update the POSTGRES_PASSWORD key
accordingly to ensure Compose reads the intended value.


# Neo4j (Knowledge Graph)
# Format: neo4j/<password>
# REQUIRED: Generate password with `openssl rand -base64 24`
NEO4J_AUTH=neo4j/7kJtbpJ1n1xzMX4F2EAu60K5
# REQUIRED: Generate password with `openssl rand -base64 24` for production deployments
# For development, use "neo4j/none" to disable auth (healthcheck compatibility)
NEO4J_AUTH=neo4j/none

# Meilisearch (Full-text Search)
# REQUIRED: Generate with `openssl rand -hex 32`
# REQUIRED: Generate with `openssl rand -hex 32` for production deployments
MEILI_MASTER_KEY=

# MinIO (S3-compatible Object Storage)
# REQUIRED: Generate with `openssl rand -base64 32`
# REQUIRED: Set unique username for production deployments
MINIO_ROOT_USER=
# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
MINIO_ROOT_PASSWORD=

# Qdrant (Vector Database)
Expand Down
16 changes: 16 additions & 0 deletions pmoves/env.tier-llm
Original file line number Diff line number Diff line change
Expand Up @@ -92,3 +92,19 @@ OLLAMA_URL=http://ollama:11434
# Cloudflare Workers AI
CLOUDFLARE_ACCOUNT_ID=
CLOUDFLARE_API_TOKEN=

# ============================================
# Additional Provider Keys (Optional)
# ============================================

# Moonshot AI (Kimi)
# Optional: Add your Moonshot API key
MOONSHOT_API_KEY=

# Venice AI
# Optional: Add your Venice API key
VENICE_API_KEY=

# Z.AI (GLM)
# Optional: Add your Z.AI API key
Z_AI_API_KEY=
12 changes: 5 additions & 7 deletions pmoves/env.tier-media
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,17 @@ NATS_URL=nats://nats:4222

# ----- MinIO (Media Storage) -----
MINIO_ENDPOINT=minio:9000
MINIO_ACCESS_KEY=minioadmin
MINIO_SECRET_KEY=minioadmin
# REQUIRED: Set unique access key for production deployments
MINIO_ACCESS_KEY=
# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
MINIO_SECRET_KEY=
MINIO_SECURE=false
MINIO_BUCKET=assets
MINIO_OUTPUT_BUCKET=outputs

# ----- Supabase (Metadata) -----
SUPA_REST_URL=http://host.docker.internal:65421/rest/v1
SUPABASE_SERVICE_ROLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.fake_key_replace_with_real
SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here

Comment on lines 9 to 21

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Empty placeholders can override layered env values.
If this file is loaded after env.shared, the blank assignments will clobber valid credentials. Consider commenting them out by default or moving them to an example file to avoid accidental overrides.

🔧 Safer placeholder pattern
-# REQUIRED: Set unique access key for production deployments
-MINIO_ACCESS_KEY=
-# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
-MINIO_SECRET_KEY=
+## REQUIRED: Set unique access key for production deployments
+# MINIO_ACCESS_KEY=
+## REQUIRED: Generate with `openssl rand -base64 32` for production deployments
+# MINIO_SECRET_KEY=
@@
-SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here
+# SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here
🤖 Prompt for AI Agents
In `@pmoves/env.tier-media` around lines 9 - 21, The file defines empty
environment variables (MINIO_ACCESS_KEY, MINIO_SECRET_KEY,
SUPABASE_SERVICE_ROLE_KEY, etc.) that will override valid values when loaded
after env.shared; update the file to avoid accidental clobbering by either
commenting out those empty assignments (e.g. replace MINIO_ACCESS_KEY= with #
MINIO_ACCESS_KEY=) or moving them into an example/template file (e.g.
env.tier-media.example) and leave this file with only non-sensitive defaults
(MINIO_ENDPOINT, MINIO_SECURE, MINIO_BUCKET, MINIO_OUTPUT_BUCKET, SUPA_REST_URL)
so runtime secrets aren’t overwritten. Ensure references to MINIO_ACCESS_KEY,
MINIO_SECRET_KEY, and SUPABASE_SERVICE_ROLE_KEY are adjusted accordingly in
deployment docs or load order.

# ----- PMOVES.YT -----
YT_CHANNEL_CHECK_INTERVAL=3600
Expand All @@ -32,7 +34,3 @@ FRAME_SAMPLE_RATE=5

# ----- Indexer Namespace -----
INDEXER_NAMESPACE=pmoves

# ----- Invidious (from GitHub Secrets in production) -----
INVIDIOUS_HMAC_KEY=temp_test_key_please_replace_from_gh_secrets
INVIDIOUS_COMPANION_KEY=temp_test_key_please_replace_from_gh_secrets
9 changes: 5 additions & 4 deletions pmoves/env.tier-worker
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,15 @@ MEILI_API_KEY=${MEILI_MASTER_KEY}

# ----- MinIO (Object Storage for Documents) -----
MINIO_ENDPOINT=minio:9000
MINIO_ACCESS_KEY=minioadmin
MINIO_SECRET_KEY=minioadmin
# REQUIRED: Set unique access key for production deployments
MINIO_ACCESS_KEY=
# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
MINIO_SECRET_KEY=
MINIO_SECURE=false

# ----- Supabase (Metadata Storage) -----
SUPA_REST_URL=http://host.docker.internal:65421/rest/v1
# Generated for fresh start (replace with your real key from Supabase)
SUPABASE_SERVICE_ROLE_KEY=1e5ac31b15768d88851879d4a6ed7b3fd64056b4f72eadca8ae62b4dafd0a6e7
SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here

# ----- Open Notebook (for notebook-sync) -----
OPEN_NOTEBOOK_API_URL=http://host.docker.internal:5055
Expand Down
Loading