Update .env.example

[Caiuriuller]

Closes # .

What

Explain the changes you’ve made.
It doesn’t need to be fancy and you don’t have to get to technical, yet.
Just explicit prose on your net change will typically suffice.

Why

The “why” is sometimes more important than the “what” of a code change,
but we tend to put it after the “what” since we aren’t evaluating theory,
we’re evaluating tangible code changes.

How

Of course, the PR diff will tell most of the story of the “how”,
but make sure to draw attention to the significant design decisions.
You decided to write a recursive method instead of a loop,
pointing out the merits of this will help the reviewer understand
your reasoning and in turn provide a better review.

[Caiuriuller]

HUB-6