At the time of creating this request, the watch: true feature does not support using anything other than sources: []. I would like to configure a task that works with the watch: true feature to check for a LISTENING port.
Ideas:
- Allow the
watch setting to accept a boolean or a nested cmd/cmds. The result of custom shell command execution could determine when a task needs to be executed.
- Upgrade the watch implementation to respect the existing
status setting, allowing runs of custom commands without a need to change the schema.
- Implement
watch: true with port: 8080, where the listening check would be a part of the watch task implementation.
At the time of creating this request, the
watch: truefeature does not support using anything other thansources: []. I would like to configure a task that works with thewatch: truefeature to check for a LISTENING port.Ideas:
watchsetting to accept a boolean or a nestedcmd/cmds. The result of custom shell command execution could determine when a task needs to be executed.statussetting, allowing runs of custom commands without a need to change the schema.watch: truewithport: 8080, where the listening check would be a part of the watch task implementation.