Tool upload and download

Tool upload

After we encapsulate a own tool by using docker image (go to ‘What is docker’ to learn about the production of tool image), we can use the following command to push the tool image to the corresponding project.

# Note:push the tool image in the local mirror warehouse to the corresponding project, and named the tool .
# fkit createTool [IMAGE_NAME] [TOOL_NAME]
./fkit createTool ubuntu16.04:latest demo

After uploading the tool image, you need to configure the command line/input file/output file/default parameters/default operating model of the tool on the FlowHub page. For details, please refer to the document ’how to make a tool’.

Tool download

For the tools you upload to the FlowHub website, you can pull and download them through the fkit tool. You can use the following command to pull the tool image to the local docker warehouse.

Pay attention that the subscribed tools cannot be downloaded locally.

# enter from the corresponding folder which Create a tool locally
mkdir demo_tool
cd demo_tool

# note: Pull tool image fkit pull [tool name: version number]
./fkit pull demo:1

The tool name and version number correspond to the tool name and version information in the Tool section of the FlowHub page.

A successful tool pull will add a new image to the local mirror warehouse. When you use the docker images command to view, you can find that the REPOSITORY of a mirror is the name of the tool image you pulled, and the TAG is the version number of the tool you pulled (before pulling Please check whether there is a mirror name with the same name in the local mirror warehouse. If there is a mirror with the same name, no new mirror will be added). At the same time, a run.ini file is generated in the current directory. You can configure the run.ini file to complete the local test and run of the tool. please refer to the document of ‘How to make a tool’ and ‘Local running and testing of tools'.