Today's 🤡 task: figuring out how "localhost:3000" snuck into one of the critical production links...

FUUUUUUUUU

🤡🤡🤡🤡🤡🤡🤡🤡

Already found in a config...

guess I'm done for the day?

🤡

At least it wasn't hard coded

Works on my PC 🤷‍♂️

Check who introduced it into the config file via Version control(like "git blame").

Nice, took less than 2 days for the clown phase to return. But legit how did this happen o.o

WTF????? I can’t even try to be that retarded with all the booze in the world

@TeachMeCode try harder, slacker!

@lungdart ok (slips a brain eating amoeba in his ear)

@TeachMeCode makes one youtube video a day and wonders how anyone can make such mistakes

@fullstackcircus owns 3 SaaS apps as a solo dev and laughs when he makes suchs mistakes

we are not the same

@fullstackcircus I never uploaded anything to YouTube. I came here to point out the idiot who hardcoded localhost:3000 you mentioned

@fullstackcircus ah, wait, you were talking about yourself? Oh….ok then 🫢. Hehe…sorry (you said you laugh when you make such mistakes, meh that’s ok the more experience you have the more you fuck up)

ah was confusing you with sidtheITkidorwhatever

you both sound the same

@fullstackcircus @SidTheITGuy

@fullstackcircus was it a copy paste mistake from a local config file to a prod config file - or a default config that had to be overridden but wasn't?

In general config files can be such a sneaky source of mistakes cause you could have a great test suite... But that of course runs on it's own config. And even with smoke tests in pre-prod or prod there's only so much you can test before the tests become flaky.