onyerleft wrote:
You can blame it on homebrew if you like
I assume it is homebrew since you referenced a directory tree in /usr/local that does not exist by default. You could have also screwed up the configuration. Considering how simple it is, Homebrew is the most likely explanation.
It still sounds like the configuration is screwed up. Assuming Homebrew is at all functional, you should be able to configure the Homebrew files to use your home directory too. At least, you should be able to in theory. Usually when people have Homebrew problems, their command line is pretty much down for the count.
I will have a development platform that allows me to design not only the necessary HTML, CSS, and Javascript, but build the databases and content management systems that tie it all together.
Then you'll have to go through all of this again with PHP and MySQL. Any instructions you find on the internet, including my own, will not apply to your Homebrewed system. Apparently, Homebrew itself has no support as people always seem to come here with Homebrew problems.
Where does the "1998" condescension come from?
Memories...
My clients wax ecstatic about their reliability, speed, and functionality - and until they don't, I'll probably continue to rely on those dead-end technologies, Apache/PHP/MySQL, to design, build, and test them.
If you've got people willing to pay the bills, then go for it. For me, web sites are not a profit centre, they are an advertising and support cost. I still run my REST services on Apache/Perl/MySQL, but I do not recommend that to others. The cost for me to switch is more than the cost to continue it for a few more years. But my new projects that have a viable future in them will not be doing that.
Re: AWS, I wouldn't go near it. In 2012 I developed a site for a luxury womenswear franchise, and in the first week after launch it disappeared into thin air. Worse, tech support was non-existent.
In my experience, it became increasingly difficult to find any web host that supports those old-school LAMP systems. Even hosting providers that had been rock-solid for years just fell apart. They were serving my web sites at almost dial-up speeds and didn't know why. They also seemed frighteningly ignorant about basic networking.
I really didn't want to use AWS and tried virtually every other option but finally just gave up. I'm willing to suffer for my principles, but only to a point. I run my LAMP services on AWS Lightsail, which is essentially the same as a traditional web hosting service. But in some cases, you can access much more powerful AWS service from your Lightsail hosts. As for the web site itself, SSL certificates alone are worth the switch to AWS Cloud Front.
If AWS goes down in 2023, no one is going to be concerned about your luxury womenswear site. They will have far more bigger problems to deal with. For smaller-scale outages, you can configure your AWS services to run in multiple zones and regions for more reliability. But those old-school LAMP sites generally aren't compatible with that unless you do a lot more work.