Workbench » History » Version 7

Tom Clegg, 07/09/2014 11:47 AM

1 1 Tom Clegg
h1. Workbench
3 5 Tom Clegg
Developer documentation:
* [[Hacking Workbench]]
5 7 Tom Clegg
* [[Workbench UI images]]
6 5 Tom Clegg
7 4 Tom Clegg
Workbench is the primary browser-based tool for Arvados users. In addition to providing built-in generic browsing tools for data and analysis jobs, Workbench acts as a gateway and integration point for analysis and visualization applications running in VMs on the cloud.
8 1 Tom Clegg
9 4 Tom Clegg
The built-in browsing features in Workbench are also available via command line tools or any other SDK; Workbench does not need any special privileges[1]. The browsing features are offered for two reasons:
10 1 Tom Clegg
11 4 Tom Clegg
* *Convenience* — Sometimes it's quicker to click than to type, and sometimes it's helpful to see progress bars instead of ASCII art.
12 1 Tom Clegg
13 4 Tom Clegg
* *Example* — The source code is an example of how to use Arvados and the Rails SDK.
14 1 Tom Clegg
15 4 Tom Clegg
The Arvados API and authentication system facilitate a smooth user experience and effective data sharing when working with multiple independent web-based applications.
16 2 Tom Clegg
17 4 Tom Clegg
Workbench is built with Ruby on Rails using the Arvados Rails SDK.
(In a sense, Workbench is the web browser SDK -- but we don't call it that because we don't expect anyone to write an application by scripting a web browser.)
21 6 Tom Clegg
fn1. Exception: Each site has a Workbench installation which is trusted enough to see the authentication tokens _for a user who is logged in to that Workbench._ This gives the user a way to obtain authentication tokens for API clients/environments that aren't well suited to the OpenID/OAuth2 authentication process, like CLI tools.