raa-parser_poster/RAA.md

RAA Parser/Poster

RAA is a separate deployment copied from the FN-8 parser/poster codebase.

Runtime

• Local workspace: D:\DEVELOPMENT\raa-parser_poster
• Public admin domain: https://raa.panel.f-n8.ru
• Gitea repo: http://192.168.1.135:3000/exostring/raa-parser_poster.git
• Coolify project: n8_parser / production
• Coolify app: RAA admin, UUID korokrhpoyqxf0nw2y8vk7lp
• Coolify DB: raa_parser_db, UUID m9v14hzfh5mk9kelxzcqvhc6
• Coolify destination: vk-parser-lxc, CTID 105, IP 192.168.1.105
• Edge proxy: Caddy in CTID 110 proxies raa.panel.f-n8.ru to Coolify Traefik at 192.168.1.105:80.
• Health check: https://raa.panel.f-n8.ru/health
• Site poster must stay disabled until a site adapter is configured.
• The current site-poster adapter boundary is site_poster_provider; only ghost exists in code today. WordPress should be added as a code adapter, not as arbitrary executable code stored in settings.

Current Deployment

Created on 2026-08-03.

• App and Postgres are managed by Coolify, not by manual Docker Compose.
• Runtime env/secrets are stored in Coolify resource environment variables.
• APP_SECRET_KEY, DB password, and initial admin password were generated in Coolify and are not committed.
• Initial admin login is admin.
• vk-parser, vk-storage-uploader, and daily-report default to disabled for a fresh RAA DB.
• Site poster defaults to disabled; do not enable it until an RAA site provider is chosen.
• A temporary manual LXC deployment was created first at CTID 107, then replaced by Coolify. CTID 107 is stopped and is not the active runtime.

Deploy Notes

To update this deployment:

1. Push changes to the Gitea repo.
2. Coolify should deploy RAA admin from gitea/main.
3. Manual deploy trigger, if needed:

curl -X POST -H "Authorization: Bearer <coolify-token>" \
  -H "Content-Type: application/json" \
  -d '{"uuid":"korokrhpoyqxf0nw2y8vk7lp","type":"application"}' \
  "http://192.168.1.135:8000/api/v1/deploy"

4. Verify https://raa.panel.f-n8.ru/health.

First-Run Settings

Set real secrets in env, not in git:

• APP_SECRET_KEY
• ADMIN_BOOTSTRAP_LOGIN
• ADMIN_BOOTSTRAP_PASSWORD
• DB_*
• TG_BOT_TOKEN
• TELEGRAM_API_ID
• TELEGRAM_API_HASH
• VK_ACCESS_TOKEN or VK_GROUP_ACCESS_TOKEN

Set runtime settings in the admin UI/DB:

• TG_MEDIA_CHANNEL_ID
• tg_poster_bot_token
• tg_poster_chat_id
• vk_poster_owner_id
• site_poster_enabled=false
• site_poster_provider=""