6 ms·
"...sometimes php developers commit configuration files..." needless jab, imo.
by leeoniya 14y ago
"...sometimes php developers commit configuration files..."
needless jab, imo.
- CiaranR 14y agoYeah could easily be applied to Perl dev's too
- leeoniya 14y agohow about "any devs" or even "novice devs". as if there's some class of super-devs that's immune to versioning mistakes, ffs.
- bastijn 14y agoAll phpers are now offended? haha, must be true than!
- leeoniya 14y agololwut? had it said "ruby" or "python", there'd be a shortage of tear gas and cars would be burning in the streets.
- edem 14y agoLet's just abstract away the details and say something like: "...sometimes <arbitrary_programming_language> <arbitrary_programming_job> commit configuration files..."
- brokenparser 14y ago"adverb adjunct noun verb adjunct noun"
- myhf 14y agogit-adverb adjunct noun verb adjunct noun
- deleted 14y ago[deleted]
- nthj 14y agoyes. This is the first thing I fix on most Rails projects I inherit. Hardly exclusive to PHP.
- mostlystatic 14y agoOh dear, you aren't supposed to commit configuration files? Is this a security thing? What's the proper way to distribute config files to to the server and other developers? "sometimes php developers commit configuration files and things that are used in production where they shouldn’t be." Not sure if I'm parsing this correctly. Should the files not be in production or should they not be committed? Is this just about overwriting the development configuration in the config file?
- philjackson 14y agoAn example scenario might play out thusly: Fred checks in the production configuration credentials (lets say mysql configuration for this example) in a file called passwords.php. Senior developer Bob Van Gogh checks out the project but needs to connect to his local mysql instance to develop. He edits the configuration file and hacks away on his feature. Somewhere along the way he accidentally commits passwords.php with his changes. Eventually his code is deployed and suddenly the app servers can't connect to the database. Bob's no good at football but he's a good developer and now thanks to that accident his reputation is tarnished beyond the football pitch too. Configuration like that should be managed by something that isn't susceptible to these accidental changes. As you mention it, security is an issue too. The fewer people who know the passwords to anything the better and the more you can keep the passwords from going over the wire the better.
- mostlystatic 14y agoCool, thanks for the explanation. I usually have the development config in the repo and the deployment script overwrites it on the server.
- prodigal_erik 14y ago
- deleted 14y ago[deleted]