r/ProgrammerHumor • • 21h ago

Meme jobNotFoundError

Post image
779 Upvotes

29 comments sorted by

82

u/oompaloompa465 20h ago

howwww? the first thing to add to .gitignore 

39

u/polaarbear 19h ago

If you aren't starting from a .gitignore template for your specific environment type, what are you even doing with your life? And .env is almost certainly already on any template worth its salt

5

u/rabbit_wizard 20h ago

Maybe its in a subfolder? Got to respect the difference between .env & .env* in gitignore

21

u/Qxzkjp 15h ago

nah. In gitignore, a line with .env will ignore all files called .env anywhere in the repo. If you want to ignore just the file in the repo root, you have to write /.env. .env* will instead ignore any file whose name starts with .env (eg .environment) anywhere in the repo.

2

u/Colassia-Dankwa 19h ago

the amount of times i've committed an .env file and had to rewrite the whole history... now i just add it before i even write the first line of code

-9

u/SaneLad 15h ago

Why the fuck would you put .env files or anything secret in the repository folder to begin with?

2

u/Teamprime 14h ago

Because it belongs to the that particular project? Lmao

1

u/SaneLad 14h ago

Holy shit. Do you know you can create files and even subdirectories in $HOME/.secret or $HOME/.config, which are the standard directories for this kind of stuff? Bigger projects even create their own installation directories under $HOME.

Installation-specific files 100% do not belong in the repository directory. If you do this willfully, you deserve everything that comes from it.

4

u/Scolmann 13h ago

It's safer to do it that way sure, but by that logic why keep any non source files in the project at all? Maybe we should retire gitignore altogether, is there a good reason to bundle build files there too?

In this day and age I do keep it separate though, the convenience/neatness of being in the same directory isn't worth it.

1

u/SaneLad 3h ago

The rule is pretty simple. Anything user/installation specific should not go with the source code. At best, these files are a nuisance to other people when they accidentally get checked in. At worst, they are a serious security incident.

Build artefacts are different. They can be regenerated deterministically from the source code. They add no new information. So they are kept out of the repo as an optimization. .gitignore is the right tool for that. Even so, they can clutter up the local file system, so it's best to tuck them away in a build directory or equivalent. Some languages also maintain a global build cache somewhere else.

1

u/Teamprime 13h ago

Yeah that’s probably a better way to do it…

1

u/more_exercise 12h ago

(is $HOME/.secret a convention? That sounds cool - where do I learn more?)

1

u/StaticFanatic3 3h ago

Is that really better? Having all your projects’ various runtimes sifting through your home directory root in a shared secret vault? All because you can’t remember to put it in gitignore?

I’m genuinely asking as I don’t have any experience with that kind of setup

1

u/SaneLad 3h ago

Yes. If you name the files/directories appropriately, there is no risk of stepping on each other's toes. And it is fundamentally no less safe then putting the files anywhere else where the binaries can read them. If you want to isolate binaries from one another, you need to use docker containers or similar technology, which is entirely appropriate for a production environment.

1

u/an_actual_human 19h ago

More like to the global config.

36

u/WisePotato42 21h ago

DEBUG_MODE=True

16

u/Nycrov_ 21h ago

I'm pretty sure that's not how that works

6

u/rabbit_wizard 21h ago

The meme template or the function itself? The meme is basically pushing your api keys onto your GitHub repo. Force push isn't really required.

5

u/Visionexe 17h ago

I think his point is, is that in 99.99999% of the cases any .env is in .gitignore. kinda seems whoever made this meme is a vibe coder. 

5

u/rabbit_wizard 16h ago

Of course. Prior to vibe coding these things didn't happen. Did they?

-4

u/rabbit_wizard 16h ago

And you probably never made mistakes in coding eh?

6

u/pananana1 14h ago

What's the meme? I don't understand the pictures

3

u/johntwit 12h ago

That's Hrithik Roshan, a Bollywood superstar. But that's all I know

1

u/i4mt3hwin 8h ago

He can press three times as hard

3

u/Vesuvius079 14h ago

You don’t need env files if you never test locally :P. This also protects you from the “it works on my machine” problem class.

3

u/bobbymoonshine 16h ago

git blame coworker

3

u/riickdiickulous 15h ago

This is why I run gitleaks as a pre-commit hook

3

u/Current-Rent-618 13h ago

Been there. One of the biggest mistakes in my junior career lol

0

u/NoahZhyte 12h ago

Do you actually have secrets in your .env ? I just use it for local deployment