exostring/new_vk_parser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add project branding and poster footers

Browse Source
This commit is contained in:
Your Name
2026-08-04 17:06:48 +05:00
parent ad66f2ed73
commit a8db1b379e
10 changed files with 134 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MULTI_PROJECT.md
+5 -1
View File
@@ -17,7 +17,7 @@ Goal: keep one codebase and run separate deployments for each editorial project.
- `ADMIN_SITE_TITLE`
- `ADMIN_APP_TITLE`
- `ADMIN_FAVICON_PATH`
- `ADMIN_FAVICON_PATH` as an optional fallback only
- `DB_HOST`, `DB_PORT`, `DB_NAME`, `DB_USER`, `DB_PASSWORD`
- `APP_SECRET_KEY`
- `ADMIN_BOOTSTRAP_LOGIN`, `ADMIN_BOOTSTRAP_PASSWORD`
@@ -35,6 +35,10 @@ Goal: keep one codebase and run separate deployments for each editorial project.
Sources, target groups/channels, poster tokens, schedules, prompts, categories, and enabled workers should stay in `app_settings`, `sources`, `content_categories`, and `worker_controls`.
Project favicon is uploaded from the admin UI and stored per deployment at
`uploads/branding/favicon.png`. If it is absent, the app falls back to
`ADMIN_FAVICON_PATH`, then to the repository `favi.png`.
Common publication hashtags are also per-project database settings:
- key: `publication_common_tags`