Do you often call the same long commands? Do you need some secrets or configurations to access the same data warehouse across many projects?
Invest time in setting up the default configuration of your shell (eg,
~/.zshrc file if you have zsh).
If you use long commands (eg, different versions of Python or Julia), give them an alias that you can call directly,
eg, add the following line
alias myapp='conda run -n my-app-environment python3 /some/long/path/myapp.py -g -r' and you'll never have to type this command again. You can simply call
If you use a GIT repository that requires SSH access, it's nice if your shell remembers your password (see Start SSH agent on login)
Automatically load your credentials into the environment variables
add the following line
source ~/.secrets.sh to your configuration file (eg,
create the file
~/.secrets.sh and add the following lines
# DATABASE CONNECTIONS export DB_ORACLE_IP="..." # add your details export DB_ORACLE_USERNAME="..." # add your details export DB_ORACLE_PASSWORD="..." # add your details # you can even have aliases for the same value export MYDB_PASSWORD=$DB_ORACLE_PASSWORD #it will mirror the value above
- Now, try accessing these values from the shell (
echo $DB_ORACLE_IP), python (
os.environ["DB_ORACLE_IP"]), or Julia (
On the last point, there are several benefits:
You'll drastically reduce the risk of accidentally publishing a file with your passwords (eg,
It's easier for your collaborators (and cloud jobs) to set up their own credentials and the code will magically run for all of you
You can use them across Python/Julia/? without any specialized parsers
Start using pipx for all Python-based CLI applications (eg, AWS CLI, black, flake8, jupyter, language servers, mlflow)
A lot of Python-based applications ask you to "simply install with pip" (eg,
pip install ABC). Unfortunately doing that will change all relevant python packages in your global environment (ie, break things)!
You could create small environments for each application to be able to independently remove them / update them. That is exactly what pipx does for you (and more)!
Try it out! On macOS:
brew install pipx pipx ensurepath
Before Julia, having clean environments was not easy. If you use Python, the closest thing you can get is Mamba.
It makes creating and managing separate environments for Python easy and unlike Conda it's really fast.
Read more: Installation instructions
Install juliaup to install and automatically update your Julia version as well as to switch between different versions.
Installing it on a mac or linux is as simple as
curl -fsSL https://install.julialang.org | sh
Similar to the theme of setting up your terminal with configurations, you can do the same for your Julia.
You can have all frequently used packages loaded automatically when you start Julia REPL by adding them to a file called
# what text editor to use when edit() is called # "code" assumes you can call VS Code from your shell ENV["JULIA_EDITOR"] = "code" using Pkg import REPL using OhMyREPL using TheFix;TheFix.@safeword fix true using BenchmarkTools using Revise @async begin # reinstall keybindings to work around https://github.com/KristofferC/OhMyREPL.jl/issues/166 sleep(1) OhMyREPL.Prompt.insert_keybindings() end # automatically activate a project environment if available if isfile("Project.toml") && isfile("Manifest.toml") Pkg.activate(".") end
Save this file in
~ is your user's home directory). You will thank me later.
If something isn't working, you can suppress loading startup.jl by starting Julia with
There are a few packages that haven't made it to my startup.jl file yet, but I would suggest you consider them:
Term.jl for displaying available methods with
JET.jl to catch silly errors in your scripts. See video from JuliaCon 2021
JuliaSyntax.jl Exciting new syntax parser that will give you much better error messages. I'm waiting for version 0.1. Check out the JuliaCon 2022 video
Downsides: Slightly slower start-up time of Julia REPL (if you add too many packages)
No beginner should ever start here, but it might happen in the first weeks/months.
There is an infamous waiting time for the first time a command runs (eg, waiting for the first plot) or, in general, waiting for Julia REPL with your startup.jl file. If you find it frustrating, use PackageCompiler.jl docs to create a system image (=Sysimage) with all these packages and functions you use preloaded and precompiled.
There is an alternative solution below.
Downsides: Lost flexibility / ability to easily update (eg, you won't be able to easily update your Julia or those precompiled packages)
Following on from the previous point, there is a different way to mostly avoid the "time-to-first-X" (ie, the first compilation).
You can use persistent sessions with tmux (=Terminal MUltipleXer, or others like Screen, Dtach, Abduco+Dvtm). Persistent means that instead of closing Julia REPL every time, you just disconnect and later on reconnect. It will remember all your loaded functions, variables, packages, etc.
Note: This is incredibly useful if you use Julia REPL as your super-calculator / Excel replacement.
Open your shell
tmux and a new window will open
julia to start Julia REPL and print something, eg,
Now disconnect from this session by pressing
CTRL+b followed by
d, and your screen show disappear (/switch back to the previous shell)
tmux a and you should see your Julia session with "Hello" printed
Read more: Quick and Easy Guide to Tmux
Downsides: None (except for the layer of complexity)