storkit: create 399_story_cli_port_flag_with_project_toml_persistence
This commit is contained in:
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
name: "CLI --port flag with project.toml persistence"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Story 399: CLI --port flag with project.toml persistence
|
||||||
|
|
||||||
|
## User Story
|
||||||
|
|
||||||
|
As a developer, I want to set the server port via a --port CLI flag that persists to project.toml, so that I don't have to remember an environment variable on every run.
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] storkit --help shows a --port option
|
||||||
|
- [ ] storkit --port 4000 starts the server on port 4000
|
||||||
|
- [ ] After first run with --port, the port is saved to project.toml
|
||||||
|
- [ ] On subsequent runs without --port, the port from project.toml is used
|
||||||
|
- [ ] CLI --port overrides the value in project.toml
|
||||||
|
- [ ] Default port is 3001 when neither --port nor project.toml port is set
|
||||||
|
- [ ] STORKIT_PORT env var continues to work as lowest-priority fallback
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user