Thanks iDemonix, Just to clarify the comments that read like Ansible advertisements are later down in the page now.
The script of the link (that I wrote) is intended as a starting point for a clean and secure web server setup without a third-party ops product - basically what you wrote “ where you could achieve the same in a few lines.”.
Rather than a few lines though the script from the line has a lot of checks and makes needed config updates. Since it’s a single script with no dependencies a developer or devops can easily copy it and modify it for their needs or environment.
I'm a noob at config management but I like the control and visibility bash gives me and I could never get the Ansible idea of 'state' to work. There seemed to be too many edge cases.
The script of the link (that I wrote) is intended as a starting point for a clean and secure web server setup without a third-party ops product - basically what you wrote “ where you could achieve the same in a few lines.”.
Rather than a few lines though the script from the line has a lot of checks and makes needed config updates. Since it’s a single script with no dependencies a developer or devops can easily copy it and modify it for their needs or environment.