-
Notifications
You must be signed in to change notification settings - Fork 19
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
conda: document environment files #281
Comments
I'm going to aim to add the following:
|
We should include details/examples of the following options:
|
Easy to add. Will do.
I don't know very much about these things. Will @datamel be able to fill me in?
Done this |
I'll try to take a stab at the JupyterHub and Configurable HTTP Proxy stuff when we make the next release (can't really document right now as we haven't sorted it out yet, just jotting it down so we don't forget). The Lab stuff is literally just adding We could document a couple of the most useful plugins, the SSH authenticator will likely be essential for a few setups. We will provide our own SSH spawner though. |
O.K. I'll add the differing python versions and JupyterLab and flesh out the docs a little by adding the commands used to create the nvs then leave the rest for now. |
@oliver-sanders - did #293 add enough that you'd close the issue? |
Not yet, still need to cover the hub, configurable-http-proxy, etc, see above comments. Will do after the next uis release (as that will change installation instructions), we haven't got a conda-forge PR up to handle the change yet. |
Closed by #342 |
We should document some example Cylc stack installations in the form of Conda environment files.
See cylc/cylc-admin#130
As an added bonus we could build these environments as part of the test battery to make sure they don't break.
The text was updated successfully, but these errors were encountered: