Haha, good one Rene. *laughs* Okay, let's consider the other options too. Option A seems like it might work, but I'm not sure I like the idea of storing the password hash instead of the actual credentials.
That's a solid solution. That way, we can keep the credentials secure and still have them accessible when we need them. *chuckles* I wonder if the exam writers have a sense of humor, though. Might as well throw in a joke about composer while we're at it.
Good point, Catarina. I'm leaning towards option B - adding the COMPOSER_AUTH variable on the project level and making it visible during the build phase.
I agree, keeping sensitive information like that out of the repository is a good security practice. But how do we do that without breaking the build process?
Okay, let's break this down. The goal is to remove the auth.json file from the project repository, right? That makes sense, we don't want to expose our composer credentials.
Alyce
10 days agoRene
12 days agoVincent
13 days agoCatarina
14 days agoVeronique
16 days agoArminda
18 days ago