Workers won't run (Windows)

[diegoRodriguezAguila]

Hello, I've followed all the steps in the docs and my jobs are being enqueued, I can see them with redis-cli monitor and at http://localhost:8000/resque/queue/default. But when I try to run
php app/console bcc:resque:worker-start default
nothing happens and shows the following:

Starting worker nohup php  D:\SGO Elfec\SGO-GestionMoviles-BackEnd\app/../vendor/chrisboulton/php-re
sque/resque.php > D:\SGO Elfec\SGO-GestionMoviles-BackEnd\app\logs/resque.log 2>&1 & echo $!
Worker started WORK-PC:$!:default

Also tried: php app/console bcc:resque:worker-start default -vvv -f
but with the following error:

Starting worker php  D:\SGO Elfec\SGO-GestionMoviles-BackEnd\app/../vendor/chrisboulton/php-resque/r
esque.php
"nohup" is not recognized as an internal or external command,
operable program or batch file.

Thank you in advance for your help.
Specs:

• Windows 7 64bits
• Php 5.5.12
• Symfony 2.8
• Redis 2.8
• BCCResqueBundle 1.1.7

[mrbase]

I'm not sure it was ever tested on or intended to run on windows.

[danhunsaker]

So, PHP-Resque itself runs on Windows (though due to major differences in the basic OS design between Windows and *NIX, it is fairly crippled in a few ways), but the startup command used in the BCC bundle is built solely for *NIX systems. I recommend using a Linux VM for running your worker(s) - as long as they can talk to your Redis server, your workers can run literally anywhere - regardless of where you run the rest of your app.

(I also recommend avoiding PHP development on Windows directly in general; instead, either developing entirely inside a VM, or using a project like Nanobox to keep repos on your Windows box while running the code in a VM, will make your overall developer life considerably easier. But that's my general automatic advice on that matter.)