Add Dagster orchestration and reduce active brands in backend
This commit is contained in:
@@ -152,6 +152,23 @@ DATABASE_URL = os.getenv(
|
||||
# 0 disables the loop, leaving the startup run and POST /api/system/brand-sync.
|
||||
BRAND_SYNC_INTERVAL_SECONDS = int(os.getenv("BRAND_SYNC_INTERVAL_SECONDS", "300"))
|
||||
|
||||
# ---------------------------------------------------------------------------
|
||||
# Active brands (development working set)
|
||||
# ---------------------------------------------------------------------------
|
||||
# Comma-separated brand names that the application and every pipeline operate
|
||||
# on. BLANK OR UNSET MEANS EVERY BRAND IS ACTIVE - that is the backwards
|
||||
# compatible default and the way to switch this feature off again.
|
||||
#
|
||||
# Nothing is deleted when this is set: the other brand_* tables and their
|
||||
# embeddings stay in the database untouched, they simply stop being discovered.
|
||||
# Going from 3 brands to 5, 10 or all of them is an edit to this one line.
|
||||
#
|
||||
# Names are resolved through resolve_parent_brand + _sanitize_name, the same
|
||||
# two steps that pick a product's storage table, so "Tata" here activates
|
||||
# brand_hindustan_unilever exactly as ingesting Tata products would.
|
||||
# See app/services/active_brands.py.
|
||||
ACTIVE_BRANDS = os.getenv("ACTIVE_BRANDS", "")
|
||||
|
||||
# ---------------------------------------------------------------------------
|
||||
# S3 / DigitalOcean Spaces (product image storage) - optional
|
||||
# ---------------------------------------------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user