Had issues getting the video_scheduler.php working with multi sites.
The INSTALL.txt file suggests that you just put the site url after the video_scheduler.php. It looks like there needs to be a -s example.com with the site name matching the folder name exactly. Thus a -s www.example.com would not work, even though normally drupal will check the base folder name.
I also think it might be helpful to give an example with increased memory usage. We are moving around some very large files (over 1GB), and with cloud files module (which shove the entire file into memory before sending it) gets very memory intensive.
Have finally settled on this command:
php -d memory_limit=3000M -d error_reporting=E_ALL\|E_NOTICE\|E_STRICT -d display_errors=stderr video_scheduler.php -s example.com
Lastly, would suggest a note about whether the video_scheduler.php handles collisions. Do I need to worry about the cron stepping over itself it a file takes a long time to convert or is that handled ok? It looks like it is because the status gets changed to a 5 (in Progress), but would be nice to have confirmation.
Comments
Comment #1
rurri commentedUpdate: We have had some issues with site slowing down during transcoding, so we have added the nice command which helps immensely.
Comment #2
Jorrit commentedI will probably remove video_scheduler.php in the future in favor of the drush command. I don't know if drush supports memory limits.
Comment #3
rurri commentedSounds good. You can specify a separate memory limit for crush by creating a ~/.drush/php.ini file with separate memory limits. So perhaps it would be worth a mention about that in the INSTALL.txt with a link to the drush page on how to do it, and perhaps a suggestion on using nice. I am pretty sure most users will want not want web performance to take a hit to a background transcoding process. The nice -n 19 will also work when spawning the drush command.
So looks like I better switch over to the drush version of the video_scheduler.php
Comment #4
Jorrit commentedI have improved the script by allowing any site to be set with the --site option. I also added some checks to verify that the option that was given was correct. Example: when you have www.yoursite.com and the files are in sites/default, you can now give --site www.yoursite.com.