Build a zen command-line environment

TL;DR

This article aims at learning how to install lovely command-line tools in a recoverable way.
You'll be able to multiplex zsh terminals over a UDP connexion (using mobile shell):

The reader is strongly encouraged to browse thoroughly the Dockerfile put in reference,
which steps summarize how to build the premises of such a text-only environment.

Disclaimer: To some extent, you might feel a bit dizzy because of the specially crafted mise en abyme.
The dizziness is a typical side effect of linux container abuse...
No worries, the feeling will just vanish with time (or you might just end up killing the wrong processes).

Dot files

Each and every user of linux distributions (or similarly flavoured operating systems)
might take a minute or two to acknowledge the significance of their own dot_files.

Even though they are hidden by design, I believe our productivity directly depends on the care they receive from us.

We all have heard (if not even worse) of hard drives just dying in some random boxes.
Still feeling a bit sceptical? Pretty numbers
have been published on Backblaze blog just to satisfy our curiosity.
Being a big fan of upcycling doesn't strictly imply there could be some happy ending for few choosen hard drives, anyway.

The bottom line is, the more precious and rapidly changing our data feel
and the more regular we shall have backup for them ready to be restored.
I insist on the latter part as knowing precisely
how to restore backups is the only way to really feel confident about them.

Let us see how to proceed in order to get things done i.e. hidden dot files safe.

From this point, one shall have received a positive message (Successfully built) well accompanied by a pretty hash.
These 12 characters are to be kept preciously.

Believe it or not, we are done already here or better said,
our personal shell has been set up according to our container building script (Dockerfile).
The pretty hash identifies a docker image which can now be run in order to use our command-line interface.

In a nutshell,

Installing a custom-tailored command-line environment only took us the time of making some notes
in the shape of a Dockerfile about what needs to be customized.

Executing a single command was enough to restore our command-line environment personalized over time

Fellows of little faith are absolutely right in showing doubts about this so let us run the interactive shell
(within a container within a vagrant box), in order to proceed, one just needs to execute the following commands