2.4 KiB
2.4 KiB
Multi-project setup
Goal: keep one codebase and run separate deployments for each editorial project.
Target model
- One canonical git repository for application code:
http://192.168.1.135:3000/exostring/new_vk_parser.git. - One canonical local workspace:
D:\DEVELOPMENT\new_vk_parser. - One Coolify application per project.
- One Postgres database per project.
- Project differences live in Coolify env variables and database settings, not in code.
- The old RAA local copy
D:\DEVELOPMENT\raa-parser_posterand old RAA Gitea repo are not the source of truth.
Per-project env
ADMIN_SITE_TITLEADMIN_APP_TITLEADMIN_FAVICON_PATHDB_HOST,DB_PORT,DB_NAME,DB_USER,DB_PASSWORDAPP_SECRET_KEYADMIN_BOOTSTRAP_LOGIN,ADMIN_BOOTSTRAP_PASSWORDVK_ACCESS_TOKENVK_GROUP_ACCESS_TOKENVK_STORAGE_GROUP_IDVK_OAUTH_CLIENT_IDVK_OAUTH_REDIRECT_URIVK_OAUTH_ORIGINTG_BOT_TOKENTG_MEDIA_CHANNEL_IDLOCAL_BOT_API_URL
Per-project database settings
Sources, target groups/channels, poster tokens, schedules, prompts, categories, and enabled workers should stay in app_settings, sources, content_categories, and worker_controls.
Common publication hashtags are also per-project database settings:
- key:
publication_common_tags - FN-8:
#новости_снаряжения - RAA:
#raa_news #страйкбол - The app posts these tags before category/source tags in TG/VK/MAX social posters.
RAA current social targets:
- raw media Telegram channel:
tg_media_channel_id=-1004312015562 - final Telegram publication channel:
tg_poster_chat_id=-1001303630155 - VK owner:
vk_poster_owner_id=-36860851,vk_poster_from_group=true - More RAA-specific runtime notes are in
RAA.md.
Poster modules
The site poster is selected by site_poster_provider. A project can disable the worker or leave the provider empty when there is no website poster yet. New website integrations should be added as provider modules behind the same interface instead of branching the worker by project name.
Current Status
- FN-8 Coolify app
n6cnr60anmruiwkiey0pukyepoints tonew_vk_parser.git, branchmain. - RAA Coolify app
korokrhpoyqxf0nw2y8vk7lppoints tonew_vk_parser.git, branchmain. - Both projects should deploy from the same commit SHA.
- Keep only env and database settings different between projects.
- Do not add project-specific defaults to migrations or
.env.example.