whiteducksoftware / whiteducksoftware/flock

[1.0] Wire CLI serve to the standard server components

Open
#435 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
120
Forks
14
Avg merge
19h 32m
Merged PRs (30d)
8

Description

The CLI serve path constructs BaseHTTPService without components, so configuration exposes only FastAPI documentation routes instead of the normal application API.

Scope

  • Reuse the existing standard server composition from the CLI path.
  • Keep established configuration, lifecycle and shutdown behavior rather than introducing a second server stack.
  • Give a meaningful startup error when the configured service cannot be assembled.

Acceptance criteria

  • A deterministic CLI/server smoke check exposes the expected application API routes rather than only /docs and /openapi.json.
  • The configured prefix and applicable authentication settings reach the actual server.
  • Startup and shutdown finish cleanly without requiring a model API key.

Boundaries

Loading a user's application factory and the full onboarding example are a dependent slice.

References

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the CLI serve path in src/flock/cli.py with the standard composition in src/flock/orchestrator/server_manager.py and the service behavior in src/flock/api/base_service.py. Run a deterministic CLI/server smoke check, then verify that application routes, the configured prefix, applicable authentication, and clean startup and shutdown work without a model API key.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.