Files
metabuilder/workflow/plugins/python/web/web_register_route/package.json
johndoe6345789 bd15b564e3 feat(packagerepo): complete workflow-based Flask server
Packagerepo can now boot its entire Flask server from a workflow definition.
No more procedural Python - the whole app is declarative JSON.

New Features:
- web.register_route plugin - Registers Flask routes that execute workflows
- server.json - Complete server definition as workflow (6 routes)
- server_workflow.py - Boots Flask server by executing server.json

Architecture:
1. web.create_flask_app - Create Flask instance
2. web.register_route (×6) - Register routes → workflows
3. web.start_server - Start Flask on port 8080

Each route maps to a workflow:
- PUT /v1/.../blob → publish_artifact.json
- GET /v1/.../blob → download_artifact.json
- GET /v1/.../latest → resolve_latest.json
- GET /v1/.../versions → list_versions.json
- POST /auth/login → auth_login.json

Benefits:
- 95% code reduction (957 → 50 lines)
- Add endpoints without code (just JSON)
- No restart needed for workflow updates
- Visual DAG of entire server architecture
- Multi-language plugin support

Usage:
  python packagerepo/backend/server_workflow.py

The entire Flask application is now workflow-based!

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-22 15:16:56 +00:00

17 lines
473 B
JSON

{
"name": "@metabuilder/web_register_route",
"version": "1.0.0",
"description": "Register a route on a Flask application",
"author": "MetaBuilder",
"license": "MIT",
"keywords": ["web", "workflow", "plugin", "flask", "route"],
"main": "web_register_route.py",
"files": ["web_register_route.py", "factory.py"],
"metadata": {
"plugin_type": "web.register_route",
"category": "web",
"class": "WebRegisterRoute",
"entrypoint": "execute"
}
}