feat!: pyfly management port (app 8080 / mgmt 9090); pyfly from GitHub v26.06.103 - #34
Merged
Merged
Conversation
…y from GitHub v26.06.103 BREAKING: business API moves 8400 -> 8080 (pyfly.server.port); actuator (/actuator/*) and admin (/admin) now serve on the separate management port 9090 (pyfly.management.server.port). Healthchecks/K8s probes/Prometheus target 9090. - pyfly consumed from git tag v26.06.103 (was local editable path); floor >=26.6.103. - pyfly.yaml/config.py/env default to 8080; management.server.port: 9090; worker health server defaults to 9090. Dockerfile EXPOSE 8080 9090; compose maps both for the API + worker management ports (9091/9092); all healthchecks -> 9090. - main.py: pyfly.web.host -> pyfly.server.host. - Python SDK: optional management_url so health() targets :9090 (back-compatible). - Full 8400->8080 / actuator->9090 sweep across docs, Python+Java SDK docs/examples, scripts. Release v26.6.10.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Adopts pyfly v26.06.103's separate management port and standardises flydocs on the canonical ports 8080 (business API) + 9090 (management).
Breaking changes
8400→8080(pyfly.server.port)./actuator/*) + admin (/admin) → management port9090(pyfly.management.server.port). Health checks, Kubernetes probes and Prometheus must target:9090. SetPYFLY_MANAGEMENT_SERVER_PORT=8080to collapse back to a single port.Changes
pyflynow consumed from git tagv26.06.103(was a local editable path), matching thefireflyframework-agenticpattern; floor>=26.6.103. uv resolves it from GitHub (the vendoringsedno-ops on a git source, exactly like agentic).pyfly.yaml(server.port: 8080,management.server.port: 9090),config.py(port=8080,worker_health_port=9090),main.py(pyfly.web.host→pyfly.server.host).EXPOSE 8080 9090; compose maps both for the API and each worker's management port (9091/9092); all healthchecks probe:9090/actuator/health/readiness.management_urlsohealth()targets:9090(back-compatible; unset →base_url).8400→8080/ actuator→9090across docs, Python+Java SDK docs/examples, and scripts (~35 files).Verification
Local gate green:
ruff check+ruff format --check,pyright(0 errors), unit suite 292 passed, Python SDK suite 156 passed. pyfly verified installing fromgit+…@v26.06.103.Ships as v26.6.10.