nebari-dev / nebari-dev/nebari-docs
[DOC] - add example configurations for each cloud
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Preliminary Checks
- This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions
Summary
It would be good to have example configs of recommended nebari-config.yaml files for each cloud deployment. Ideally the base example would feature a small, medium, and large user instance size and a small and large gpu instance size. We could additionally either add comments to these examples to explain why certain choices were made or come up with other configurations for other scenarios (ex. low cost deploy, high availability deploy, etc)
Steps to Resolve this Issue
- Write example config for AWS
- Write example config for GCP
- Write example config for Azure
...
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 existing Nebari documentation and any current nebari-config.yaml examples in the repository. Define examples for AWS, GCP, and Azure covering small, medium, and large user instances plus small and large GPU instances; done means each cloud has a documented recommended configuration, with the rationale or deployment scenario explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100