Fix: Update Signal Handling for Unix-like and added Windows Systems support

[yourchocomate]

laravel-reverb.mp4

Fix: #65
Fix: #74

Description
This PR enhances the signal handling mechanism to support both Unix-like systems and Windows. It introduces support for SIGTSTP on Unix-like systems and implements Windows-specific signal handling using sapi_windows_set_ctrl_handler. This update improves the platform compatibility of the application and ensures proper signal handling across different operating systems

Changes Made

• Added SIGTSTP to the list of subscribed signals for Unix-like systems to not suspend process without gracefullyDisconnect the opened server
• Introduced a new method handleSignalWindows() to handle signals on Windows.
• Implemented Windows-specific signal handling using sapi_windows_set_ctrl_handler.

Testing

• Tested on Unix-like systems to ensure correct handling of SIGTSTP.
• Tested on Windows to verify proper signal handling using sapi_windows_set_ctrl_handler.

Any feedback or suggestions for improvement are welcome.

[luisprmat]

This is the issue in windows that this PR solves.
It worked for me, but making that modification.

[mfrizky]

I still get the same error in docker environment with php 8.3.4 fpm-bookworm in my development server. This problem doesnt occure to me on my local machine with windows OS non docker environment.

[yourchocomate]

I still get the same error in docker environment with php 8.3.4 fpm-bookworm in my development server. This problem doesnt occure to me on my local machine with windows OS non docker environment.

I will check it out, Can you provide the docker config you have used?

[mfrizky]

Sure, here are my docker-compose.yml and Dockerfile of my php :
Dockerfile.txt
docker compose yml.txt

Update :
my lead come up with a solution to use pcntl in Dockerfile like this
RUN docker-php-ext-configure pcntl --enable-pcntl \ && docker-php-ext-install pcntl
the reference probably from this site :
https://laracasts.com/discuss/channels/laravel/reverb-installation-issue?page=1&replyId=930286

Thank you and sorry for the trouble 🙏