[1] https://conda.io/docs/user-guide/tasks/manage-environments.h...
[1] https://conda.io/docs/user-guide/tasks/manage-environments.h...
I have just started using Conda locally to learn before taking it to work. I'm a new sysadmin and my predecessor maintained a restricted list of python packages on all cluster systems like a dictator. I don't want to be one.
Does conda cloning the environment mean I can just copy the project directory to another server and expect my program to run without it looking for the packages on the internet?
EDIT: Yeah, just tried it again, it rewrites the shell files so everything works again. It even uses the same python version as you used.
conda create -n myenv python=3.6.3
conda install -n myenv scipy
conda install -n myenv numpy
conda install -n myenv pandas
source activate myenv # To make use of the environment.
source deactivate
conda create --name myclone --clone myenv. # Clones the environment.
du -sh /Users/asampath/anaconda3/envs/myclone
du -sh /Users/asampath/anaconda3/envs/myenv
813M /Users/asampath/anaconda3/envs/myenv
Fat environments. But, this works out just fine in our NFS mounted storage in cluster.
If you use packages from conda channels (which are repositories of packages), then it should work flawlessly. Usually basically everything is available from either the official channel (anaconda) or some community channel (like conda-forge). At least in the data-science domain. I'm not really familiar with the python web-development scene, so not sure about that.
Edit: actually once I had to copy an environment from one machine to another (because of connection problems), and I seem to recall that worked too, but I don't think this method is officially supported.
Snatching defeat from the jaws of victory :)
But I'm not sure who to believe, the other reply to the parent comment says that copying things around is actually possible.