feat(cli): added cli support for project initialization

[Winay-Chowdary66]

Add CLI support for project initialization

I've been working on adding CLI functionality to make it easier to bootstrap new servc projects. This was something that came up a few times where I wanted a quick way to get started without having to copy-paste boilerplate code.

What's new

• servc init command - Creates new projects with different package managers (uv, poetry, pip)
• Interactive prompts - Asks for project name, package manager choice, etc. Pretty smooth UX imo
• Multiple templates - Each package manager gets its own template with proper configs
• Auto dependency installation - Can install deps after project creation

How it works

# Basic usage
servc init my-service

# Interactive mode with immediate setup
servc init my-service --interactive --immediate

# Different package managers
servc init my-service -t uv
servc init my-service -t poetry
servc init my-service -t pip

The templates include all the basic stuff - worker.py, config, health checks domains, proper pyproject.toml/requirements.txt

Technicals

• Built with asyncclick for the async CLI stuff
• Used pyclack for the nice interactive prompts (spinners, selections, etc.)
• Cross-platform (tested on Windows, should work fine on Linux/Mac)
• Proper error handling.

Package manager support

• UV (recommended) - Fast, modern, handles venvs automatically
• Poetry - Full dependency management with lock files
• Pip - Standard approach with requirements.txt
• Each one creates the appropriate project structure and configs.

What's next

Could add more templates in the future, maybe shell completion, but wanted to get the core functionality out first and see how we can use it.

[drgroot]

Overall good, I think the test cases is most important here!

[drgroot]

please remove these, the idea of excluding all pip modules if for security reasons, it ensures that the user/consumer chooses the amount of risk they want to expose themselves to. very important in an enterprise environment!

[Winay-Chowdary66]

Right, but without these the CLI may not work. The user has to explicitly install these for it to work. If that is fine then i will remove them in here and add them to requirements.txt for the unit tests for work.

[drgroot]

Hmm, i wonder then if we need to bundle this as a separate pip module then, enterprise environments aren't usually happy with dependency changes, it clobbers up their SBOM.

[Winay-Chowdary66]

nice, do you think we could do something like servc[cli]. And the cli can be installed separately with, decoupled from core svc logic

pip install servc[cli]

[drgroot]

test cases?

[Winay-Chowdary66]

I'm researching on writing tests for CLI tools, bit a tricky here.
For the templates, I could add a scenario to verify templates are copied to target directory but I will have to think on adding tests to verify the installation and dev server works.
I will add the unit tests.

[drgroot]

@Winay-Chowdary66 please move to the new repo here:
https://github.com/serv-c/servc-cli