Anytime a hello-work tutorial starts with running a command that generates 50 boilerplate folders/files, I die a little inside.
Anytime a hello-work tutorial starts with running a command that generates 50 boilerplate folders/files, I die a little inside.
You can install PHP with homebrew or macports and still do this. I use it all the time.
https://www.php.net/manual/en/features.commandline.webserver...
This is pretty quick and painless to setup. SLES had a single command for it back when I used it, if I remember correctly. I currently have a simple Ansible playbook for it on RHEL.
It’s certainly much more straightforward than deploying Flask to production, especially if just using the default document root and not getting into virtual hosts.
I thought about going to nginx once, but as I started looking into it, I had to stop myself and ask why, as Apache was more than adequate for what I was doing, I had no issues with it in the past, and the setup was dead simple. It would be change for the sake of change, and seemed more annoying to boot, to your point.
I think a lot of people build everything assuming it will be the next Facebook, when it’s not. This leads to a lot of complexity in the name of potential future scale that never comes. For some, they are building the dream, but for an internal enterprise tool, mostly geared toward one team (which filtered out a little beyond into the org), I’m not worried about it.
The current setup has been running for 10 years now with minimal maintenance. Just moving it as needed to avoid EOL operating systems and platforms. For something that is a nice-to-have and never felt like a main deliverable for my job, this is ideal.
I almost rewrote it in python once, and planned to host that with nginx, but then I came to my senses.