[Iplant-api-dev] Installing applications for use with the AGAVE API

[Lawson, Peter]

I have a general question about the process of installing applications to interface with AGAVE API. WIth Foundation my understanding of application installation was derived from the documentation below:

Basic Application Development
To develop one of these applications, the requisite binaries, files, and resources are hosted in a subdirectory of a user's $IPLANTHOME iRODS directory, along with a special Bash-language script describing how the user code communicates with the iPlant job management system.
If the application under development is a simple script or is comprised of pre-compiled binaries that will run on a TACC resource, development of this directory can proceed on a local system that has the ability to use iRODS icommands and to GET/POST HTTPS from the command line | Tutorial |.
If the application needs to be compiled, takes special advantage of the software stack or physical architecture of the target HPC system, etc, the developer must first secure an XSEDE account and log onto the desired system before beginning development. Developer may then write scripts, compile and install requisite software, and test the command-line and batch-mode invocation of that software | Tutorial |.

Does this documentation also apply to the AGAVE API aside from changes in JSON to allow for interfacing with AGAVE? Thank you for your assistance and I apologize if this is a simple question that could have been answered by the AGAVE documentation.

-Pete L.