All Categories (1-6 of 6)

1. Allow people to test a tool that is installed but not published?

   Closed | Responses: 0

   I have a tool which the admin has installed but I have not yet published. I'm wondering how I can allow VHub users (that I decide) to gain access to the tool for testing/feedback...

   https://theghub.org/answers/question/43

2. Create a Ghub tool with Rappture builder

   Note that while this functionality is still available, we recommend using the Jupyter Notebooks (jupyter6deb10) tool to develop user interfaces for your Ghub tools. Refer to the Jupyter Examples...

   https://theghub.org/kb/development/create-a-hub-tool-with-rappture-builder

3. Tool development workflow

   This workflow describes how a Ghub user may develop, test, troubleshoot, and deploy a new tool on the Ghub site. This workflow assumes the user has developed the tool using the C language; the tool...

   https://theghub.org/kb/development/tooldevelopmentworkflow

4. Hub Tool Directory Structure

   When developing tools, use the recommended Ghub tool directory structures and save yourself some grief.Ghub Application Space Directory StructureThis is the actual directory structure of your...

   https://theghub.org/kb/development/directorystructure

5. Ghub Tool Directory Structure

   When developing tools, use the recommended Hub tool directory structures and save yourself some grief. Hub Application Space Directory Structure This is the actual directory structure of your...

   https://theghub.org/wiki/GhubToolDirectoryStructure

6. Hub Tool Directory Structure

   19 Sep 2012 | Posted by Jeanette Sperhac

   When developing tools, use the recommended Hub tool directory structures and save yourself some grief. ==Hub Application Space Directory Structure== This is the actual directory structure of your...

   https://theghub.org/members/2153/blog/2012/09/hub-tool-directory-structure