Panicking hard these days. I don't get devops at all.
I get the overall concept what it is, but I am not sure why my current project is using it. Honestly don't get why they cant copy these files to the server, run chmod and chown, start a few Linux services, host the damn app and move on to the next project. Seems like a whole lot of effort for nothing. If something was to be done a dozen times per day it would make sense to create a pipeline and have sprints to verify that all the small details get covered. But that's not the case here. tc: 143K
The key part about devops is to automate everything. I bet you're not familiar with Dockers and Kubernetes, why start a few Linux VM and waste tons of resources, how about distributing workload for the apps. There's a lot of things to consider here when you need to scale a service.
The essence of what you described is sound. But like Hashicorp said, developing the infra and automating the pipelines, app config, etc, makes an SWE’s life much easier.
Your idea doesn't scale, at all. It's also about reproducibility. I would rather have a button to promote from QA to Prod, I don't want to have to get the sysadmin to copy files over and possibly introduce downtime because he fat fingered something.
Wut