I'm working on a web project that executes CLI commands to perform running tasks to spare users from having to wait since PHP/Apache combo cannot (to my understanding) create a separate process for said long-running processes.

  • Is the this the best approach for running long for running long processes that do not force web users to wait?

  • Is there any time-bombs one needs to look out for when taking this approach (running many CLI processes from PHP/Apache?

  • How would your users get to know the status of their long running task? How would they know when it has finished? What would happen if your server gets flooded with requests for these long running processes? – Bart van Ingen Schenau Jan 21 at 10:33

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.