Add CLI command to browse registry environments
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 9
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 33
Description
Summary
Discovering available public environments currently requires the desktop app or server UI. A CLI equivalent would make it easier for new users to get started without setting up the UI first. Something like:
$ nebi registry browse nebari-environments
REPOSITORY TAG VISIBILITY
nebari_environments/data-science-demo 0.1.0 public
nebari_environments/web-demo 0.1.0 public
nebari_environments/qwen3-4b 0.1.0 public
$ nebi import quay.io/nebari_environments/data-science-demo:0.1.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CLI command registration and the existing registry or import handling used by nebi. Trace how registry data is retrieved, then run the current CLI tests or commands before defining coverage for the new browse command. Done means the command lists public environment repositories with tags and visibility and supports the displayed import reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100