I see humanity as it exists today as a cancer on the planet and it's not out of smugness. The pursuit of infinite growth is ruining everything that's beautiful around us.

We can discuss the semantics of the word nature all you want but it is just shifting the focus from the actual problem, which is how we destroy everything we touch. Which is also what I'm assuming GP means.

I don't see a reason to ever pass them. Sensitive production values should never be accessible to everyone, and for development the team should be able to create them themselves.

I usually keep very stupid values in .env.example, with the instructions to `cp .env.example .env`. In development it doesn't matter if the password is "password". In production the privileged admin sets up actual values.

> - non-sensitive environment variables also need a home. I don't like the idea of cluttering the project with a .env.local or worse like .env.development.local

`cp .env.example .env` and the application uses .env just like in production, only with dummy values.

In philosophy there is a debate regarding the meaning of the word nature and if humans should be considered a part of it, and I see the points, but that's a different discussion.

Other species co-exist in the eco-system, we destroy it.

[1]: https://blog.codeberg.org/codeberg-launches-forgejo.html

[1]: https://www.passwordstore.org/

For a long time Docker was helpful and opened exposed ports on the firewall. So you wanted to access your redis ports locally and exposed it on the container? Now everything in there is accessible on the open internet.

I believe they've fixed it but I haven't used Docker in years so I wouldn't know.

What is the problem with that? How would you write that snippet? It is common in the new functional js landscape, even if it is pass-by-ref.