funboost-funweb-ops

Operate funboost message queues through the built-in Flask web management interface.

892|166|Updated Dec 25, 2021
One-click install
npx skills add https://github.com/ydf0509/funboost --skill funboost-funweb-ops-ydf0509
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: funboost-funweb-ops
Source: https://github.com/ydf0509/funboost/tree/main/.agents/skills/funboost-funweb-ops
Command: npx skills add https://github.com/ydf0509/funboost --skill funboost-funweb-ops-ydf0509

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires funboost, flask, gunicorn.

What problem does it solve? Running distributed task queues without visibility makes it hard to monitor consumers, retry failed messages, and manage scheduled jobs. This Skill guides you through starting and using funboost's built-in Flask web console (funweb) so you can inspect queue depth, consumer status, consumption curves, and re-deliver failed messages from a browser. ## Core Features & Use Cases - Web Console Startup: Launch the management UI via python -m funboost.funweb.app or start_funboost_web_manager() in code, with correct PYTHONPATH and Redis configuration. - Queue Operations: View queue depth, clear queues, inspect online consumers by IP or queue name, and read full BoosterParams configurations. - Failure Recovery & Scheduling: Re-deliver failed messages from the function result table, and manage APScheduler cron/interval/date jobs stored in Redis. - Use Case: A team runs Redis-backed funboost consumers across multiple machines and needs a single dashboard to watch consumption rates, find which worker died, and re-run failed tasks without touching code. ## Quick Start Ask the AI to start the funboost web manager on port 27018 with heartbeat and result persistence enabled so you can log in at http://127.0.0.1:27018 and inspect your queues.

Frequently Asked Questions about funboost-funweb-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start the funboost web management interface?▼

Install funboost[flask], set PYTHONPATH to your project root containing funboost_config.py, then run python -m funboost.funweb.app or call start_funboost_web_manager() in code. The console is available at http://127.0.0.1:27018 with default login admin/123456.

How do I retry failed messages in funboost?▼

Open the function result table page in funweb, locate the failed records, and click the re-run action to re-deliver those messages. This requires MongoDB result persistence enabled via function_result_status_persistance_conf in BoosterParams.

Why does the funboost web console show no queues or consumers?▼

The console reads runtime data from Redis heartbeats, so consumers must set is_send_consumer_heartbeat_to_redis=True in BoosterParams and be actively running consume(). Also verify PYTHONPATH points to the directory containing funboost_config.py with correct Redis settings.

Does funboost funweb require MongoDB to work?▼

No, MongoDB is optional and only needed for the function result table and consumption rate chart pages. Queue operations, consumer lists, alerts, and timed job management work with Redis alone.

Can I manage funboost scheduled tasks from the web UI?▼

Yes, the timed jobs page lists, adds, edits, deletes, pauses, and resumes APScheduler jobs with cron, interval, or date triggers stored in Redis. It is recommended to keep the web-side scheduler paused and run the actual scheduler in your consumer script via ApsJobAdder.