-
Notifications
You must be signed in to change notification settings - Fork 30
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
Update conda-store docs #399
Conversation
✅ Deploy Preview for nebari-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Note from community meeting - Add additional note about installing packages with xref: nebari-dev/nebari#2191 |
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.
Just had a few things to expand on, but otherwise looks good!
|
||
![conda-store UI - Sample environment build details page: showing the conda environment artifacts](/img/tutorials/conda_store_build_details_bottom.png) | ||
* `analyst` namespace - Users in the `analyst` group can view and `admin` group can view+edit the environments in this namespace | ||
* `developer` namespace - Users in the `developer` and `admin` groups can view+edit the environments in this namespace |
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.
I'm pretty sure developer is required for access to the dask workers.
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.
I was about to suggest some changes, but noticed this will be confusing with the keycloak roles and the concepts of namespaces intertwined, so I will think about how to rewrite this a bit
|
||
Please keep in mind that these are _NOT_ available to Dask workers! | ||
::: | ||
Include the [`nebari-dask` metapackage](https://anaconda.org/conda-forge/nebari-dask) in your environment to use Dask. This ensures you have the correct version of `dask-gateway` and the latest versions of `dask` and `distributed` libraries. |
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.
Add note that the nebari-dask metapackage version should match nebari version
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.
also note again here that you have to be in the develop group to be able to access dask.
|
||
Navigate to the `Full Logs` to investigate in more detail. Also, from the build status page you can trigger re-build in | ||
case you hit issues with intermittent outages, etc. | ||
Include the `jhub-apps` package in your environment to create apps using the JHub App Launcher. You will also need the relevant app development framework and other necessary packages in the environment. |
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.
You don't need jhub-apps itself. You need jhsingle-native-proxy>=0.8.2
for all apps.
For panel apps you'll also need bokeh-root-cmd>=0.1.2
in additional to the panel deps.
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.
The app launcher now has its own docs which explain the environment requirements. I think its safe to remove this here.
I will do a last passtrough here in will merge, thanks @pavithraes @kcpevey |
Co-authored-by: Kim Pevey <kcpevey@quansight.com>
Co-authored-by: Kim Pevey <kcpevey@quansight.com>
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.
LGTM
I will fix the conflicts and merge this, as we need to at least remove the old docs on this matter. I will open a follow-up issue about what needs to be addressed. |
Reference Issues or PRs
Closes #197
What does this implement/fix?
Put a
x
in the boxes that applyTesting
Documentation
Access-centered content checklist
Text styling
H1
or#
in markdown).Non-text content
Any other comments?
With the updates, this page may not belong in "tutorials".
Should be merged after #397 and conda-incubator/conda-store#726