nebari-dev / nebari-dev/nebari-docs
[DOC] - Expand deployment instruction on pre-existing infrastructure
Open
Nobody has claimed this yet.
area: documentation 📖
- 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
Expand How to deploy Nebari on pre-existing infrastructure to add more cloud providers.
xref: https://github.com/nebari-dev/nebari-docs/pull/300
Steps to Resolve this Issue
- Test the workflow for GCP, Azure, and DO 💻
- Document the workflows 📝
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 with the “How to deploy Nebari on pre-existing infrastructure” page linked in the issue. Test the deployment workflow for GCP, Azure, and DigitalOcean, then document each confirmed workflow on that page. Done means the three provider workflows are tested and their instructions are available to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, gcp, kubernetes
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100