10 Matching Annotations
  1. Nov 2022
    1. Remember there are two kinds of variable. Internal Variables and Environment Variables. PATH should be an environment variable.

      In my case, I was trying to debug which asdf not finding asdf, in a minimal shell.

      I had checked bash-5.1$ echo $PATH|grep asdf /home/tyler/.asdf/bin

      but ```

      The PATH environment variable

      env | /bin/grep PATH `` being empty was the key discovery here. Must have forgotten theexport`.

    2. All shells should tell you that your path is the same thing with BOTH of the two commands: # The PATH variable echo "$PATH" # The PATH environment variable env | /bin/grep PATH
  2. Jun 2021
  3. Feb 2021
    1. STATSD_SAMPLE_RATE: (default: 1.0)

      It's recommended to configure this library by setting environment variables.

      The thing I don't like about configuration via environment variables is that everything is limited/reduced to the string type. You can't even use simple numeric types, let alone nice rich value objects like you could if configuration were done in the native language (Ruby).

      If you try to, you get:

      config/initializers/statsd.rb:8:in `[]=': no implicit conversion of Integer into String (TypeError)
  4. Jan 2021
  5. May 2020
    1. Some GitLab features can behave differently for each environment. For example, you can create a secret variable to be injected only into a production environment.
  6. Dec 2019
    1. neutrino build --require dotenv/config You can then tell Neutrino to inject these environment variables in your neutrinorc: ['@neutrinojs/env', [ 'NODE_ENV', 'APPLICATION_NAME', 'LOGIN_STRATEGIES', 'TASKCLUSTER_ROOT_URL', ]],