Server Outputs

[thinkerbot]

Redirecting output for the server is tricky.

Basic Redirection Proposal

• Redirect stdout and app log based on build, effectively creating 'runs'
• Leave stderr to console, or to daemon redirection for logging errors

This will handle use cases of building a dump file. Handles can be open/closed from the app control panel, and then the files can be accessed through app/data.

Leaving one stderr file prevents error messages from being split across multiple files.

Monitor Proposal

• Implement renderer middleware that will render to a directory/id where id will increment and render flagged tasks
• Create a directory.index partial

This basic idea allows specific tasks to render their results in an incrementing fashion. Each result can be monitored, essentially, as it comes off the task. The effect is to allow an individual task to be run without a dump, or conversely, to have the results of a task rendered in one specific way.

[thinkerbot]

Run Proposal

• Setup a controller /run/task/id
• Get print out help.erb, config.erb, input.erb, results index
• Post parse config and input. Instantiate, run via call (no app), then render result.erb using renderer
• Return rendered result with links to go again