be request

[mottosso]

goal

To facilitate the download of remote data relevant to a task.

$ be in remoteproject shot1 rigging --enter
$ be request
Username: mottosso
Password:
Pulling content from 81.53.123.59...
12% [======>                                  ] 86.12 mb  6.26m/s  EST 5 mins

Followed by be in remoteproject and having the remote skeleton downloaded, an artist may browse the hierarchy up to a particular directory and call be request which will download the corresponding content from the remote project.

The author have then explicitly associated certain paths (and optionally levels/branches within a path) with any of the criterias listed in #15 such that only authenticated users may download content that is relevant to them.

This will allow for artists to download only what they need, and authors to define exactly what is needed.

implementation

Given user credentials, an SSH key or other form of authentication, a secure connection can be made to an endpoint specified by the remote party. It is then up to the remote part to provide the infrastructure needed to actually transmit the files into the working directory of the running session of be.

Credentials are either stored from the point at which an artist enters a project, or provided with the command when called.

..but what would that infrastructure look like?