3 ms·
I mean modern devops is basically circling back around to that idea but with “php files” replaced with “git repo.” To deploy code to production at $dayjob all
by Spivak 5y ago
I mean modern devops is basically circling back around to that idea but with “php files” replaced with “git repo.”
To deploy code to production at $dayjob all that’s necessary is to commit to master and press the play button once you’re satisfied the code works in dev/qa/staging.
The pipeline is relatively complex because production ready infrastructure has some irreducible complexity but devs don’t have to care about it most of the time. In some cases we adopt a team of devs to work on infra related performance initiatives but that’s rare.
- fivea 5y ago> I mean modern devops is basically circling back around to that idea but with “php files” replaced with “git repo.” I don't agree. DevOps is and has always been a guy FTP'ing files to a server. Except that guy was smart and wrote a script that runs as a git hook to automatically run that for him. That script was so successful that the same figurative guy also integrated tests and checks and rollbacks into his script. After spending some time with the script, that guy noticed that the whole software development cycle would be far better if the software they were developing and deploying had some design features to eliminate potential problems and simplify said scripts. But in the end it's always a guy pushing files to a server. But doing it the smart way.