jij

credit: https://stackoverflow.com/questions/39356413/how-to-add-a-custom-ca-root-certificate-to-the-ca-store-used-by-pip-in-windows/52961564

>pip config set global.cert path/to/ca-bundle.crt
>pip config list  # user trusted-host
    pip.ini or pip.conf
    [global]
    trusted-host = pypi.python.org
                   pypi.org
	           files.pythonhosted.org
    cert = /etc/ssl/certs/ca-bundle.crt

jij

.bash_profile vs .bashrc
by Josh Staiger

WHEN working with Linux, Unix, and Mac OS X, I always forget which bash config file to edit when I want to set my PATH and other environmental variables for my shell. Should you edit .bash_profile or .bashrc in your home directory?
You can put configurations in either file, and you can create either if it doesn’t exist. But why two different files? What is the difference?

According to the bash man page, .bash_profile is executed for login shells, while .bashrc is executed for interactive non-login shells.

What is a login or non-login shell?

jij

http://www.computerhope.com/unix/uln.htm
Linux and Unix main page
About ln

ln creates links between files.
Syntax

ln [OPTION]... TARGET [...] [LINKNAME [...]]
Description

jij

launchctl setenv
/etc/launchd.conf
/etc/profile (system wide profile, exist, calls paths and paths.d, bashrc for shell)
/etc/paths (in use)
/etc/paths.d/* (in use)
/etc/bashrc (in use)

~/.profile (currently empty)
~/.bash_profile (in use for login shell - Mac alway lunch login shell for new window)  -- being used by me
~/.bashrc (not exists, use for non login shell)