Hacker News new | ask | show | jobs
by lordofgibbons 749 days ago
>It takes 5 minutes to configure

Is that because you have 18 years of experience, or would it be as easy for a new developer?

5 comments

I was a long-time PHP dev and then moved on to C#. I was close to writing this nginx/fpm setup lookss very complex compared to "dotnet run". But then I remembered, in ASP.NET you have a Program with 50 lines of code that must have an exact order, otherwise thinks work except they don't.

So I would say, knowing these two languages, PHP really is that easy to setup.

This has not been true for a long time.
You won’t find this answer very satisfying, so feel free to ask questions.

But it depends on what you’re trying to accomplish. If you’re sticking with defaults, it’s very easy - it’s less than ten minutes of work or seconds if you’re comfortable working with Docker.

On the other hand, let’s say that you’re running into problems scaling to handle more requests. You’ll end up having to tweak the max_workers setting. That takes a bit of experience or it can be a lot of ‘fun’ (in the Dwarf Fortress sense).

So yes and no. But a lot of people have been through this, have all the trauma you would receive and tend to be quite helpful.

You can do it!

I just have the right config for both Apache2 and nginx from hundreds of sites. The config itself is only 50 lines. You can find a good one and stick with it.
Yup. The process of finding alone will take more than 5 minutes. And is likely to not work for your particular circumstance.
You can have a a ~20 line docker-compose.yml file that only requires you to `docker compose up` and you're up and running. It's gotten insanely easy to run php-fpm + nginx + [whateverdb] in a set of docker services that require virtually no configuration.
And who is going to write that ~20 line compose file with "no configuration"? A newbie?
An LLM of course. They are really good at “trivial but you have to find a good tutorial” types of work.
When you're configuring Internet facing Linux services you're kind of out of the newbie area.

A newbie is more likely to use the built-in development server and then SFTP a 'git archive' to a shared host.

The original comment was about newbies. Everyone is a newbie at one point.

Just last year I tried a blog engine written in PHP. 24 years programming experience, but I haven't touched PHP for 10 years, and I haven't touched configuring it for 15+ years.

It took me half a day to make it work.

What blog engine? Usually with PHP applications you clone the repo, copy .env boilerplate, enter database credentials, run Composer to fetch dependencies and do some setup tasks, then boot the application.
I really wish people would maintain conversation context for at more than a single reply.
I think it would be roughly that easy for anyone with basic nginx experience. Nginx includes a php fast-cgi snippet that you just `include` from your server block.

It really is very easy.