1) Configure some software you need.
2) The software doesn't work.
3) Disable SELinux.
4) The software works.
5) F--- SELinux.
After a dozen occurrences of this pattern, your experience will have taught you to begin all deployments from step 5 ;)
On the server I usually use Ubuntu and run custom server software running in a container and never have problems.
I really don't see any reason to disable SELinux. Maybe back in RHEL5 days, but not since then. Just educate yourself on some tools. It really isn't that hard.
You may not see a reason to disable SELinux, but not all Linux systems are RHEL, and don't have it enabled to begin with. I personally would not enable it on a system that did not design for it as a default.