-
Notifications
You must be signed in to change notification settings - Fork 35
Remove DigitalOcean references in the docs #544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for nebari-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
dcmcand
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a missed reference on:
| - `do` for DigitalOcean |
and
| Currently, Nebari supports [Amazon AWS][nebari-aws], [DigitalOcean][nebari-do], [Google GCP][nebari-gcp], and [Azure][nebari-azure]. |
Also, I am guessing this would be in the release notes, but we should have a note explaining why digital ocean is gone.
|
@dcmcand thanks for the review and for catching those lingering references.
Correct. I think we should add a note to the release notes explaining this and adding an alternative for users that might still want to use Nebari in DigitalOcean (i.e., using the |
Reference Issues or PRs
This is a companion docs PR for nebari-dev/nebari#2838 and is related to issue nebari-dev/nebari#2749
What does this implement/fix?
Put a
xin the boxes that applyTesting
Documentation
Access-centered content checklist
Text styling
H1or#in markdown).Non-text content
Any other comments?