Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a --timeout parameter to run-script to override default timeout #4920
We already have https://getcomposer.org/doc/03-cli.md#composer-process-timeout - isn't that enough? It works for all commands at least.. cc @grifx
He wants to run an API server as part of this package, that implies an infinite timeout. I don't think the global timeout should have to be disabled for a single exception, be it for an infinite script or one that could run longer than the default 300 in special cases.
This PR adds the option to ignore the global default on a per instance basis (that's why it is set after the
added a commit
this pull request
Feb 16, 2016
pushed a commit
this pull request
Jan 1, 2017
referenced this pull request
Mar 14, 2017
Wondering if it would be possible to pass that to script shortcuts? i.e.
I'm just looking at this myself. We run everything inside Docker, and our dev environments have two dependencies; Docker and Composer. For example, we can run
However, if we want to have a long-running process, such as Webpack watching the files, we have a problem. We literally just enter
I want this single command to have a custom timeout. This section of our scripts looks like this:
"node":"docker-compose run --rm -w /app node", "npm-install": "@node npm install", "npm-rebuild-sass": "@node npm rebuild node-sass", "webpack": "@node webpack --watch", "webpack-compile": "@node webpack" }
Is it possible to have the timeout specified in the command, somehow? Rather than needing to pass in the longer command (which is less than ideal) or updating the entire app's timeout (even less ideal)?