- download the
.sh
files from the websites corresponding to Linux - run
bash Miniconda....sh
- allow the
init
to occur to copy the relevant source to.bashrc
- otherwise later you can do
source ~/miniconda3/etc/profile.d/conda.sh
and thenconda init
- same thing with mamba basically
conda create --name py35 python=3.7
conda activate py35
conda deactivate
conda list
conda env remove --name bio-env
conda info --envs
conda info -e
conda list --revisions
conda install --revision 2
One way is to create a text file
conda list --explicit > bio-env.txt
conda env create --file bio-env.txt
Or a YAML file:
conda env export > environment.yml
conda config --add channels conda-forge
conda config --set channel_priority strict
conda install <package-name>
As of version 4.6.0, Conda has a strict channel priority feature. Strict channel priority can dramatically speed up conda operations and also reduce package incompatibility problems. We recommend it as a default. However, it may break old environment files, so we plan to delay making it conda's out-of-the-box default until the next major version bump, conda 5.0: https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-channels.html
conda config --describe channel_priority
conda config --set channel_priority strict
- https://www.earthdatascience.org/workshops/setup-earth-analytics-python/setup-git-bash-conda/
- https://stackoverflow.com/questions/54501167/anaconda-and-git-bash-in-windows-conda-command-not-found
- I ran these two commands and it worked:
. /c/Users/<username>/AppData/Local/Continuum/anaconda3/etc/profile.d/conda.sh
conda init bash
https://docs.conda.io/projects/conda/en/4.6.0/\_downloads/52a95608c49671267e40c689e0bc00ca/conda-cheatsheet.pdf https://kapeli.com/cheat\_sheets/Conda.docset/Contents/Resources/Documents/index