Assuming the staging environment, as your example points to. You’ll want to load the console by prepending the RAILS_ENV environment variable to the rails console command. RAILS_ENV=staging rails console That should get you in. Once you’re in, you can just access the ENV variable directly. 2.2.2 (main):0 > ENV And that will dump out the … Read more
use following:- default: cv1: Foo cv2: <%= ENV[‘FOOVAR’] %>
Did you happen to open/save the file in TextEdit? That can introduce filesystem metadata (quarantine attribute) leading to the symptom you describe. Try: xattr -l /usr/local/bin/bbcolors and xattr -d com.apple.quarantine /usr/local/bin/bbcolors if you see the quarantine attribute.
Open the file in vim or vi, and administer the following command: :set ff=unix Save and exit: :wq Done! Explanation ff stands for file format, and can accept the values of unix (\n), dos (\r\n) and mac (\r) (only meant to be used on pre-intel macs, on modern macs use unix). To read more about … Read more
You want $CONDA_DEFAULT_ENV or $CONDA_PREFIX: $ source activate my_env (my_env) $ echo $CONDA_DEFAULT_ENV my_env (my_env) $ echo $CONDA_PREFIX /Users/nhdaly/miniconda3/envs/my_env $ source deactivate $ echo $CONDA_DEFAULT_ENV # (not-defined) $ echo $CONDA_PREFIX # (not-defined) In python: import os print(os.environ[‘CONDA_DEFAULT_ENV’]) for the absolute entire path which is usually more useful: Python 3.9.0 | packaged by conda-forge | (default, … Read more
In this scenario, it doesn’t sound like an env var is the way to go. Usually, you’ll want to use environment variables to give your application information about its environment or to customize its behavior: which database to connect to, which auth tokens to use, how many workers to fork, whether or not to cache … Read more
As an addition to DarkSideF answer. You should be aware that each line/command in Dockerfile is ran in another container. You can do something like this: RUN export bleah=$(hostname -f);echo $bleah; This is run in a single container.
conda-env now does this automatically (if pip was installed with conda). You can see how this works by using the export tool used for migrating an environment: conda env export -n <env-name> > environment.yml The file will list both conda packages and pip packages: name: stats channels: – javascript dependencies: – python=3.4 – bokeh=0.9.2 – … Read more