Well from my personal PoV there are a few problems with that
You can’t detect all credentials reliably, they could be encoded in base64 for example
I think it’s kind of okay to commit credentials and configuration used for the local dev environment (and ONLY the local one). E.g. when you require some infrastructure like a database inside a container for your app. Not every dev wants to manually set a few dozen configuration entries when they quickly want to checkout and run the app
I think it’s kind of okay to commit credentials and configuration used for the local dev environment (and ONLY the local one).
No. Never.
E.g. when you require some infrastructure like a database inside a container for your app. Not every dev wants to manually set a few dozen configuration entries when they quickly want to checkout and run the app
In this situation, it would be better to write a simple script that can generate fresh and unique values for the dev.
I have never had a good experience with a Debian server. Every single time I had to add unstable or third party repos to get anything remotely current to run. What’s the point if you have to add unstable shit anyway?
I’ve recently spent a fair amount of time trying to peel my blog away from my existing framework due to how much I hated using docker to just build a website, it doesn’t need to be this heavyweight.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.