Use shared AP blueprint, drop custom wellknown/actors BPs
All checks were successful
Build and Deploy / build-and-deploy (push) Successful in 52s
All checks were successful
Build and Deploy / build-and-deploy (push) Successful in 52s
Webfinger, actor profile, inbox, outbox, and followers are now served by the shared AP blueprint registered in create_base_app(). Federation keeps identity + social blueprints for UI routes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
6
app.py
6
app.py
@@ -9,8 +9,6 @@ from shared.infrastructure.factory import create_base_app
|
||||
from shared.services.registry import services
|
||||
|
||||
from bp import (
|
||||
register_wellknown_bp,
|
||||
register_actors_bp,
|
||||
register_identity_bp,
|
||||
register_social_bp,
|
||||
)
|
||||
@@ -61,8 +59,8 @@ def create_app() -> "Quart":
|
||||
])
|
||||
|
||||
# --- blueprints ---
|
||||
app.register_blueprint(register_wellknown_bp())
|
||||
app.register_blueprint(register_actors_bp())
|
||||
# Well-known + actors (webfinger, inbox, outbox, etc.) are now handled
|
||||
# by the shared AP blueprint registered in create_base_app().
|
||||
app.register_blueprint(register_identity_bp())
|
||||
app.register_blueprint(register_social_bp())
|
||||
|
||||
|
||||
@@ -1,4 +1,2 @@
|
||||
from .wellknown.routes import register as register_wellknown_bp
|
||||
from .actors.routes import register as register_actors_bp
|
||||
from .identity.routes import register as register_identity_bp
|
||||
from .social.routes import register as register_social_bp
|
||||
|
||||
2
shared
2
shared
Submodule shared updated: 38233279a2...f2262f702b
Reference in New Issue
Block a user