iex shell starts, it looks like a file
.iex.exs. It starts looking
at the current directory and if it doesn’t find one, it looks at a global one
~/.iex.exs). All the code inside the file is
loaded and added to the
IEx shell’s context, so all the modules imported,
aliases, required, and bindings from the file are accessible inside the shell.
The terminal command
!$ allows us to to retrieve the previous command in
a terminal session. This allows us to reference the previous commands and append/
prepend if to a new command instead of using ↑ and ↓ arrow keys.
Using relative line numbers is a great way to make navigation in
efficient, however, it can be a pain while pairing or when you need absolute
line numbers. One way of making this process easier is to create a key
binding which toggles relative line numbers. It can be done by adding the
following function to your
I have been deploying/running production applications for about two years now
and the first problem that comes to mind while deploying
OTP releases is
Build-time vs Run-time environment configuration. While running a
there isn’t much of a difference between build-time and run-time as you are
running the app in the same environment in which you’re compiling (building) it.
However, that might not be the case when using releases. At Annkissam, we have
come up with a few solutions to that problem which I explain better in