(-main cmd & args)
This main function is for managing tools from the command line via the
leiningen lein tools
alias.
This main function is for managing tools from the command line via the leiningen `lein tools` alias.
(force-initialise-tools)
Forcibly initialises the tool config, installing the latest version of all official tools regardless of what is currently installed.
Forcibly initialises the tool config, installing the latest version of all official tools regardless of what is currently installed.
(get-all-npm-tools)
Send an HTTP request to the NPMJS API to get a list of bluegenes tools.
Send an HTTP request to the NPMJS API to get a list of bluegenes tools.
(get-all-tools)
Return list of tools as a REST response to our GET.
Return list of tools as a REST response to our GET.
(initialise-tools)
Checks for tools config and initialises one if it doesn't exist.
Checks for tools config and initialises one if it doesn't exist.
(install-all-npm-tools)
Install all bluegenes tools from the NPM registry.
Install all bluegenes tools from the NPM registry.
Takes a request to install one or more tools.
Takes a request to install one or more tools.
(installed-tools-list)
Return a list of the installed tools in the tools config file.
Return a list of the installed tools in the tools config file.
(package-operation operation package+)
Perform a package install or uninstall operation
on package+
which can
be a single package name or a collection of multiple. Returns an error
response if a different package-operation is already in progress.
On success it will return a response with the new tool list.
Perform a package install or uninstall `operation` on `package+` which can be a single package name or a collection of multiple. Returns an error response if a different package-operation is already in progress. On success it will return a response with the new tool list.
(parse-tool tool-name)
check tool folder for config and other relevant files and return as a map of useful info. This is used client-side by the browser to load tools relevant for a given report page. A valid tool needs to have the following:
check tool folder for config and other relevant files and return as a map of useful info. This is used client-side by the browser to load tools relevant for a given report page. A valid tool needs to have the following: - package.json - config.json - dist/bundle.js
(tools-list-res)
Create response containing the list of tools along with their parsed data.
Create response containing the list of tools along with their parsed data.
Path to the tools directory containing the config file and packages.
Path to the tools directory containing the config file and packages.
Takes a request to uninstall a tool.
Takes a request to uninstall a tool.
Takes a request to update a list of tools.
Takes a request to update a list of tools.
(verify-package-params f)
Helper to wrap API functions to check for validity of package parameters.
Helper to wrap API functions to check for validity of package parameters.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close