Tutorial for Conda Migration using Miniforge #805
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Good start, I think there are a few things worth revising to make it simpler and clearer for our intended audience.
Once everything is structured as we like, we may need to clean up the screenshots to look cleaner and more professional. I've got some tricks I can show you with GIMP that I use frequently. Maybe we can do a group meeting on these tricks since they would benefit everyone.
|
|
||
| ``` | ||
|
|
||
| Replace `<new_environment_name>` with your desired new environment name. This command will read from the `environment_backup.txt` file and install the packages from the specified channels like `conda-forge` and `bioconda` channels. |
There was a problem hiding this comment.
If you say "replace <X>" for any bracketed variables, then you must do the same thing for all bracketed variables.
I think in this case, there is no need to use a bracketed name for the environment. Why not use the migrate_env.txt from earlier? I think it might be helpful to tell them to name it <your_old_environment>.txt. Then there is no ambiguity about which text file is which, in case someone decides to do them all at once.
There was a problem hiding this comment.
And these are .yml files, not .txt files.
There was a problem hiding this comment.
I tried this with the .yml files and it threw errors, so I stuck to using the .txt files for transferring the environments.
Pull Request
Created a tutorial to guide the migration of environments using Miniforge module on cheaha with the
conda-forgeandbiocondachannels.Overview
The tutorial walks a user through the steps for moving their environment containing conda packages installed using the default channels to a new environment using the Miniforge module and its channels.
Related Issues
Fixes #793