feat(server): add TLS certificate support - #230
Open
calvarado2004 wants to merge 1 commit into
Open
Conversation
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
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.
Summary
--ssl-certfileand--ssl-keyfileflags toft serveMotivation
FreeToken currently calls Uvicorn without exposing its TLS settings, so deployments must add a separate reverse proxy even when the inference server should terminate TLS directly. This adds the minimal native path while leaving existing deployments unchanged.
Testing
python -m pytest -q tests/server— 540 passedpython -m py_compile python/freetoken/server/args.py python/freetoken/server/api_server.py tests/server/test_tls_args.pyI also checked open and closed FreeToken PRs for TLS/SSL/certificate support and inspected every open PR touching the server argument, launch, or API-server paths; no overlapping implementation was found.