What problem does it solve? Manually writing HTTP APIs to publish tasks and query results for distributed queue workers is repetitive and error-prone. This Skill shows how to use funboost's built-in FaaS routers to expose publish and result-query endpoints for all @boost decorated functions without writing API code. ## Core Features & Use Cases - Built-in Web Routers: Integrate with FastAPI via app.include_router(fastapi_router), Flask via app.register_blueprint(flask_blueprint), or Django Ninja via api.add_router, automatically providing POST /funboost/publish and GET /funboost/get_result endpoints. - Publisher/Consumer Separation: Guides correct architecture where the web process only publishes tasks while worker processes run consume(), with queue metadata discovered through Redis heartbeats. - Custom API Fallback: Demonstrates manual endpoint creation with aio_push and AioAsyncResult when built-in routers do not meet requirements. - Use Case: A backend team needs a REST API so a frontend can submit email-sending tasks and poll for results; mounting fastapi_router exposes the endpoints instantly while workers consume from a Redis queue. ## Quick Start Add the funboost FastAPI router to my FastAPI app so my boosted task functions are exposed as HTTP publish and result-query endpoints.
