Skip to content

fix: warn about ~600 MB download before first server start#80

Open
nthmost-orkes wants to merge 1 commit intofix/get-all-naming-consistencyfrom
fix/download-size-warning
Open

fix: warn about ~600 MB download before first server start#80
nthmost-orkes wants to merge 1 commit intofix/get-all-naming-consistencyfrom
fix/download-size-warning

Conversation

@nthmost-orkes
Copy link
Copy Markdown
Contributor

Summary

  • Prints a "first run" heads-up message before the JAR download begins
  • Surfaces the Docker alternative for users who want a faster first-run path

User impact

First-time users who ran conductor server start would see a download progress bar appear with no warning about size or duration. On slow connections this could take 10+ minutes while the README promises "Get Running in 60 Seconds." Now users see the size and an alternative upfront, before committing to the download.

Fixes conductor-oss/getting-started#3

🤖 Generated with Claude Code

…-oss/getting-started#3)

Print a heads-up message before the JAR download begins so users
know to expect a large download. Also surfaces the Docker alternative
for users who want a faster first-run experience.
@nthmost-orkes nthmost-orkes changed the base branch from main to fix/get-all-naming-consistency April 7, 2026 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

conductor server start downloads 608 MB with no upfront warning

1 participant