There are things you don't want to, or can't do, inside a web request. It could be a task that needs to be retired if it fails, maybe one that takes a significantly long time to process, or multiple jobs that need to be processed over time. Whether you're sending an email, processing a video, or consuming Twitter's streaming API, you should be using a separate process, and probably a daemon. In this hands-on workshop, you'll learn how to stop abusing cron, and easily daemonize a PHP script that responds responsibly to process signals.

Comments

Comments are closed.

Lawrence Shea at 17:33 on 15 Nov 2017

Great speaker, obviously very knowledgeable. Had a few snafus he resolved wicked quick - so it didn't detract at all.

Joanne Garlow at 14:00 on 16 Nov 2017

Nice example code and useful information on setting up and getting daemons running.

Ryan Howe at 16:41 on 16 Nov 2017

This will great information to bring back and put to work with my team, thank you for the clear and easily understandable demos!