I'm trying to set up a watch process for multiple people that will constantly be keeping an eye on a collection of files. I understand how to get gulp.watch set up, but I need to go a step beyond and have that watcher self-start and always be running. Starting it manually leaves room for potential user error, like someone forgetting to start it before making changes. Additionaly, everyone has varying numbers of the code base checked out (for concurrent dev). This watcher would either need to be aware of all those code bases, or a unique one per each code base would have to be active. Any ideas what I could do to make this as automatic as possible? This is a small part of the work environment, so I can't have it be something that needs constant maintenance by each individual user