I wouldn't advise to set up locally on Windows just because on the live server the environment is Linux and you would STILL need to do it in Linux, so if your environment is different - even if you can make it work, you may have various bugs just because different environment setups.
You could use virtual machine on Windows, with Laravel Sail or Docker.
the simpliest way would be - adding a login page where specific users can log in and see the dashboard (the same users that would match the horizon dashboard condition)
How to handle the situation when redis suddenly stops and supervisor is unable to restart the redis server then how we re going to handle the fallback?
Hey Povilas,
Good stuff.
You should probably mention that .env QUEUE_CONNECTION value shoould be "redis" for horizon to work.
thank you, updated
what are the options when using Redis for Windows users?
I wouldn't advise to set up locally on Windows just because on the live server the environment is Linux and you would STILL need to do it in Linux, so if your environment is different - even if you can make it work, you may have various bugs just because different environment setups.
You could use virtual machine on Windows, with Laravel Sail or Docker.
Cannot tell you how good this tutorial was for me! Got Supervisor all running on my AWS EC2 instance using this guide Thanks!
HELLO HOW TO HANDLE THIS IN PRODUCTION for laravel api only how to handle Gate
the simpliest way would be - adding a login page where specific users can log in and see the dashboard (the same users that would match the horizon dashboard condition)
How to handle the situation when redis suddenly stops and supervisor is unable to restart the redis server then how we re going to handle the fallback?
Heartbeat checks might help with that, as you would instantly get notifications about this.
As far as real-solution, we rarely had this happen and often it was due to something we did, but not by itself, so I can't answer 100%, sorry!