Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Jul 4, 2025. It is now read-only.

The model management is at CLI but not API Server #1386

vansangpfiev started this conversation in Team Discussions
Discussion options

Currently, CLI and API Server can directly access model data, which means we support APIs Server for model management, but CLI only uses some of them. Should CLI only use underlying APIs?

IMO, we are building only 1 execution for both CLI and Server. Therefore, it makes sense when we use CLI without calling APIs. If CLI only uses underlying APIs, should we build 2 executable binaries, each for CLI and Server?
More context:
https://discordapp.com/channels/1107178041848909847/1204617960615055401/1290548201186660362
cc: @dan-homebrew @louis-jan @namchuai @nguyenhoangthuan99

You must be logged in to vote

Replies: 1 comment 2 replies

Comment options

@vansangpfiev Will this be similar to Docker?

  • docker-cli
  • docker-engine

Will there be any impact on our packaging and installer, if we move to two binaries?

You must be logged in to vote
2 replies
Comment options

@vansangpfiev Will this be similar to Docker?

  • docker-cli
  • docker-engine

Will there be any impact on our packaging and installer, if we move to two binaries?

I believe it will impact the packaging, installer, and updater logic also cc: @hiento09

Comment options

I see. Let's keep this for v1.0.1 then. Let's ship the existing version for v1.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /