3 ms·
Unfortunately, there is tooling, and a subculture that builds tooling, that uses configuration files in the same directory as the source code. Say you're deplo
by twic 6y ago
Unfortunately, there is tooling, and a subculture that builds tooling, that uses configuration files in the same directory as the source code.
Say you're deploying with cool-deploy-tool. cool-deploy-tool finds the password for the server by looking for a file called "Coolfile" in the project root. You have to create that file to use it. Now you have a footgun lying around.
I associate this stuff with the Ruby community, but it's spread far and wide, notably to the Node and Go communities, which i think have large Ruby emigrant populations.
As a prototypal example, consider dotenv, which began in Ruby:
https://github.com/bkeepers/dotenv https://github.com/bkeepers/dotenv
And has travelled to Node:
https://github.com/motdotla/dotenv https://github.com/motdotla/dotenv
And Go:
https://github.com/joho/godotenv https://github.com/joho/godotenv