mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
510a0e038c
The Serve CLI and REST API always sets the host to `0.0.0.0` and the port to Serve's default. This change adds `host` and `port` as top level options in the Serve config file, so users can manually set the host and port of their Serve application to different values.
This change introduces a new Serve config file format:
```yaml
import_path: ...
runtime_env: ...
host: ...
port: ...
deployments: ...
...
```
`host` and `port` are optional and can be omitted. A running Serve application's `host` and `port` cannot be changed. If a user tries to `serve deploy` a config file with different `host` and `port` options than an already-running Serve application, `serve deploy` will fail without making any changes to the application. The user must `serve shutdown` their application and restart it with `serve deploy` to change their `host` and `port`.
**Follow-Up Items**
* The following CLI commands should **not** start Serve automatically. They should check whether Serve is running and perform some sort of no-op if it's not. That would alleviate the concern that the user starts Serve by accident through a `GET` request and needs to deal with default `host`/`port` options. Corresponding docs should also be updated.
* `serve status`
* `serve config`
* `serve shutdown`
|
||
|---|---|---|
| .. | ||
| deployment-graph | ||
| doc_code | ||
| tutorials | ||
| architecture.md | ||
| architecture.svg | ||
| autoscaling.md | ||
| deploying-serve.md | ||
| deployment-graph.md | ||
| faq.md | ||
| getting_started.md | ||
| handle-guide.md | ||
| handling-dependencies.md | ||
| http-adapters.md | ||
| http-guide.md | ||
| index.md | ||
| key-concepts.md | ||
| logo.svg | ||
| managing-deployments.md | ||
| ml-models.md | ||
| monitoring.md | ||
| package-ref.md | ||
| performance.md | ||
| production.md | ||
| user-guide.md | ||
