Fire script from a different root about php-cron-scheduler HOT 4 OPEN

So I forked this and played around a bit. I found it not working on Windows because of the (' . $compiled . ') > /dev/null 2>&1 & section of Run::compile(). This isn't valid for someone running WAMP. I added a check for the OS to resolve that.

if ($this->canRunInBackground()) {
            // Parentheses are need execute the chain of commands in a subshell
            // that can then run in background
            if (strtoupper(substr(PHP_OS, 0, 3)) !== 'WIN') {
                $compiled = '(' . $compiled . ') > /dev/null 2>&1 &';
            }
            else {
                $compiled .= ' > NUL';
            }
        }

I also added some options to the config of scheduler to define a working folder to execute from that would supplant the bin if defined.

Let me know if you are interested in the fork code.

from php-cron-scheduler.

@SageDavis is the problem the path to the php bin? If so, you can set it as a second parameter so no need to worry where the script to execute is located. I would also suggest (in your case) to use absolute paths when scheduling your scripts, for example

$scheduler->php(
    '/absolute/path/to/my/script.php', // The script to execute
    '/absolute/path/to/my/custom/bin/php' // The PHP bin
);

But maybe I am not following your scenario, if so please provide an example.

About the second comment, to be honest in the beginning I didn't put any effort to make it works for Windows, thinking that if used in conjunction with the crontab that would only have been available on unix systems.

I am not familiar enough with Windows to know for sure if that code works, but I trust you saying that works. Although I have a question, would the script run in background or in foreground when doing

$compiled .= ' > NUL';

and if not, is there a way or running it in background? Otherwise the OS check might make more sense to be added on the if above

if ($this->canRunInBackground() && strtoupper(substr(PHP_OS, 0, 3)) !== 'WIN') {
  ...
}

I'd like to see your changes yes, if you can please add a link

from php-cron-scheduler.

@SageDavis Thanks for your code ! I've also been trying to make it work on Windows (have it on my local machine) and your trick definitely made the job.

from php-cron-scheduler.

@SageDavis is the problem the path to the php bin? If so, you can set it as a second parameter so no need to worry where the script to execute is located. I would also suggest (in your case) to use absolute paths when scheduling your scripts, for example

$scheduler->php(
    '/absolute/path/to/my/script.php', // The script to execute
    '/absolute/path/to/my/custom/bin/php' // The PHP bin
);

But maybe I am not following your scenario, if so please provide an example.

About the second comment, to be honest in the beginning I didn't put any effort to make it works for Windows, thinking that if used in conjunction with the crontab that would only have been available on unix systems.

I am not familiar enough with Windows to know for sure if that code works, but I trust you saying that works. Although I have a question, would the script run in background or in foreground when doing

$compiled .= ' > NUL';

and if not, is there a way or running it in background? Otherwise the OS check might make more sense to be added on the if above

if ($this->canRunInBackground() && strtoupper(substr(PHP_OS, 0, 3)) !== 'WIN') {
  ...
}

I'd like to see your changes yes, if you can please add a link

This works in the background on Windows. the challenge is that it's a console command and commands are different between OSs, as does relative references. If you are working with a php based website calling some scripts on the server itself you have to call it from the root or relative references will not work. The first comment was in relation to calling the script in a way that would still work for relative placed libraries. The second comment with the code addresses the console syntax for opening something in the background
php-cron-scheduler.zip
I did the changes local, but have attached here.

from php-cron-scheduler.