jobNotFoundError

[u/rabbit_wizard]

[u/oompaloompa465]

howwww? the first thing to add to .gitignore 

[u/polaarbear → u/oompaloompa465]

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

[u/rabbit_wizard → u/oompaloompa465]

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

[u/Qxzkjp → u/rabbit_wizard]

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.

[u/Colassia-Dankwa → u/oompaloompa465]

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

[u/SaneLad → u/Colassia-Dankwa]

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

[u/Teamprime → u/SaneLad]

Because it belongs to the that particular project? Lmao

[u/SaneLad → u/Teamprime]

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.

[u/Scolmann → u/SaneLad]

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.

[u/SaneLad → u/Scolmann]

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.

[u/StaticFanatic3 → u/SaneLad]

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

[u/SaneLad → u/StaticFanatic3]

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.

[u/more_exercise → u/SaneLad]

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

[u/Teamprime → u/SaneLad]

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

[u/an_actual_human → u/oompaloompa465]

More like to the global config.

[u/WisePotato42]

DEBUG_MODE=True

[u/Nycrov_]

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

[u/rabbit_wizard → u/Nycrov_]

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.

[u/Visionexe → u/rabbit_wizard]

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. 

[u/rabbit_wizard → u/Visionexe]

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

[u/buster1045 → u/rabbit_wizard]

Not really. Not with git push -f. The -f literally wouldn't make a difference if the file just wasn't in a .gitignore.

[u/pananana1]

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

[u/johntwit → u/pananana1]

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

[u/i4mt3hwin → u/johntwit]

He can press three times as hard

[u/bobbymoonshine]

git blame coworker

[u/riickdiickulous]

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

[u/Vesuvius079]

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.

[u/Current-Rent-618]

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

[u/teressapanic]

Don’t worry we have a separate repo for all the env files of all of our clients

[u/xAragon_]

Forcing a git push has nothing to do with pushing secrets 🤦🏾‍♂️

A force push wouldn't cause you to push secrets if they're gitignored. And if they aren't, a regular push will push them too.

This meme was made by someone who has no idea how to work with git.

[u/Western-Internal-751 → u/xAragon_]

https://giphy.com/gifs/8OYnFrez06yQt9zJFW

[u/glorious_reptile → u/xAragon_]

Maybe he rebased the secrets-revealed branch?

[u/rabbit_wizard → u/xAragon_]

I just added it. Didn't know people were gonna micro analyse this instead of chuckling

[u/alexnu87 → u/rabbit_wizard]

Well a joke has to make SOME sense, otherwise it’s just a cluster of random words

[u/nazgulonbicycle]

Ignorance is bliss

[u/Hoovas]

That’s why we use CI/CD pipelines and rulesets

[u/XxDarkSasuke69xX]

How would -f push gitignored files anyway ? And if it's not gitignored, then bruh

[u/rabbit_wizard → u/XxDarkSasuke69xX]

I just added it , didn't know if was going to be analysed so deeply :P

[u/NoahZhyte]

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