mirror of
https://github.com/Comfy-Org/ComfyUI.git
synced 2026-08-15 22:16:52 +08:00
d1014a5f92
With --enable-assets removed and the assets system always on, there is no supported way to run without it. Add an explicit opt-out for the rollout bake period: cloud multi-tenant sidecars need a guaranteed off-switch, and QA needs a clean-fallback configuration. When --disable-assets is passed: - asset API routes are registered but disabled, returning a structured 503 - database initialization is skipped entirely (no sqlite file is created; the database currently has no non-asset users) - the background seeder is disabled, covering startup, /object_info and post-execution enrich scans, and output registration - workflow output enrichment and /upload/image asset registration are skipped - the assets feature flag reports false, and supports_model_type_tags follows it since model_type tags are an assets-API capability The hidden --enable-assets no-op remains accepted for launcher compatibility; --disable-assets takes precedence since the former gates nothing.