Support for script folders

[rclough]

With complicated workflows often comes a lot of scripts (ie not just system commands) that need to be managed by a workflow system such as Dagobah.

I know personally, our way of developing scripts and deploying them will involve something like developing locally, pushing to a git repo that will automatically push the master branch of scripts and relevant files (config, etc) to our server that runs Dagobah. We can then execute the files from Dagobah.

It would be nice to have a way to tell Dagobah to look in some directory either globally, or on a per job basis, such that you can add tasks that reference that specfic deployment folder. This way instead of having to look for the fully qualified folder path on CLI then pasting into the web interface, the web UI would just have a drop down to choose scripts from. This would make tasks both easier to create as well as manage.

This would also be useful if you have a folder of scripts that do common utilities that you use in a bunch of jobs, but that could easily be resolved by adding a folder like that to your $PATH

[thieman]

I'd be interested in investigating an approach that was a little more interactive than a dropdown. You could easily have thousands of files within a large-enough directory and your scripts may be spread out in a few different sub-folders. What do you think of this flow:

1. User gives Dagobah a list of directories that may have files the user wants to reference in Tasks
2. Dagobah periodically indexes the files in these directories, optionally filtered by file extension. It may be important to limit total number of files.
3. We use something like typeahead.js to help the user find these scripts in a separate textbox during Task creation. Files still get added with their fully-qualified path.

[rclough]

Using something like typeahead would be pretty cool. It might also be useful to make sub-folder names match job title names?