But for the framework itself?

Ok. Understood. And then.

I’d like if I had time for that)

It’s too developed with years of battle tested code

*stable not developed

Don’t be so trusting. Taylor doesn’t seem to care much about privacy

Sure

I wont say he’s a Saint or something like that.

I’m just saying there really is no reason for him to do that.

Maybe for Vapour, Forge yes.

But for the framework itself?

Ok ok. It sounds real. Yet next one. Is there an overwhelming predefined controller of global “php artisian serve”? What is that? I can see processes but I can’t get how do they work

Then trust the hundreds of people who have taken time to check that

I didn’t really use artisan serve. I use Valet.

I’m not paranoid or something yet curious)

I do trust. But I was away for 8 years). Pretty much for me to run up to shortly)

I didn’t really look into the artisan serve script before. But if I were to guess, it runs a CLI command to start a PHP process that’s it

and point it to a certain port and probably some configuration to ensure route is pointed properly and other considerations

True. Yet there are specific listeners sometimes that I can’t find in doc

Zoom makes you pay and still spies on you after making hundreds of millions. Human greed knows no bounds

Routine 5m 15m, 1h and 3h

What kind of listeners are you referring to?

Are you refering to Port Listener?

I’m paranoid. You can trust me

Php cli opens port, waiting for connection for port idle time. And shutdown

That is why I am here)

the php artisan serve is really just a way for you to easily start a server to view your website on localhost. I think with the wide spectrum of ecosystem surrounding Laravel, the usage for serve is probably in it’s minimal

Ok ok. Trust you on that. Don’t bother.

I cant speak of the specific technicality of the listener functionality. But it makes sense that when you spawn a process you need to listen on the port for incoming connection right?

Just was a bit worried of why should other ports be listened

When you deploy laravel to a production server, you rely on nginx/Apache etc to run your website

If you are worried, dont use it 🙂 Try Laravel Valet

Not if it is bound officially to certain port as said in “php artisan serve –port xx

I don’t use Mac still. Lol)

I’m not sure but i think php artisan serve runs php -S localhost:8000

ok sure, I cant really defend much for “Serve” as it’s been like 6 years since I last used serve haha

I’m being very honest here