2 ms·

The thing is "yum install httpd php8 mariadb" will NOT get you a working local server stack, the extra configuration is super, duper important. Are you documen

The thing is "yum install httpd php8 mariadb" will NOT get you a working local server stack, the extra configuration is super, duper important. Are you documenting the extra configuration? What modules have you a2enmod'ed, what configs did you put in place, what permissions did they have, what firewall rules and selinux grants? What PHP config values did you adjust? Kernel parameters? Did you document all those things? Ok, great, you documented them! How are you sure your documentation is correct? Ansible is executable documentation of the above. Need to replicate the setup because your old OS is going EOL? Run the playbook. Want to make sure that when EOL time comes that your documentation is correct? Set up a test box and run the playbook. Did your machine fall over and you need to get back up in business? Did a security vulnerability compromise your machine? Set up a new machine and run the playbook. These tools provide significant value to many of us. I, for example, burn down half of our dev and staging environment every night, as long as the other half is healthy, and spin up machines from a base OS image. If our data center falls over, I have a pretty high confidence that I can bring up the bulk of our machines from a base OS image and a git repo, plus a handful of other artifacts.

0x6c6f6c 4y ago
The self-documenting nature of these tools and the ability to get many people running quickly are both extremely valuable and I don't think OP has to deal with this issue- perhaps a smaller team or just an independent approach. In a company where you have some 5+ languages with even more frameworks, various package managers, multiple data stores, etc. you're really going to be spending a lot of time just running individual commands to set up, e.g.: PHP 8.0, php-fpm NodeJS, pnpm, redis, memcached, Nginx, Elasticsearch. In total you would have probably run or configured some hundred or more commands/LOCs yourself. You run an update and all of a sudden you're PHP service is inaccessible. What now? This happens. But automated setups typically cover this scenario already so it's just working post-update, or provide means of debugging and resolving the issue. Having some projects in the team where automation is not that great and even some where it's only halfway there, I've seen developers literally lose a full day or more just because of a system. The same thing can happen with Docker Desktop - where something like Nix which declaratively documents and defines native system resources is a significant improvement over the current Docker status quo.

0x6c6f6c 4y ago

The self-documenting nature of these tools and the ability to get many people running quickly are both extremely valuable and I don't think OP has to deal with this issue- perhaps a smaller team or just an independent approach. In a company where you have some 5+ languages with even more frameworks, various package managers, multiple data stores, etc. you're really going to be spending a lot of time just running individual commands to set up, e.g.: PHP 8.0, php-fpm NodeJS, pnpm, redis, memcached, Nginx, Elasticsearch. In total you would have probably run or configured some hundred or more commands/LOCs yourself. You run an update and all of a sudden you're PHP service is inaccessible. What now? This happens. But automated setups typically cover this scenario already so it's just working post-update, or provide means of debugging and resolving the issue. Having some projects in the team where automation is not that great and even some where it's only halfway there, I've seen developers literally lose a full day or more just because of a system. The same thing can happen with Docker Desktop - where something like Nix which declaratively documents and defines native system resources is a significant improvement over the current Docker status quo.