A CLI to create JS Proxies to be able to call WebTask.io from your SPA
npm install webtaskifyCreate JS proxies to be able to call webtask.io easily from your FrontEnd app.
With npm run:
```
npm install -g webtaskify
Once it's installed, you'll be able to call the webtaskify command from your terminal.
`bash
Usage: cmd [options] [command]
Commands:
login Enter your account name and WebTask token to run other tasks
create [options] Creates the proxy files to be able to call https://webtask.io/ to run your backend task
logs [options] Logs the output of Webtask.io. Usefull for debugging tasks
Options:
-h, --help output usage information
-V, --version output the version number
`
`bash
Usage: create [options]
Creates the proxy files to be able to call https://webtask.io/ to run your backend task
Options:
-h, --help output usage information
-b, --baseUrl
-f, --files
-e, --env
-o, --output
`
`bash
Usage: logs [options]
Logs the output of Webtask.io. Usefull for debugging tasks
Options:
-h, --help output usage information
-r, --raw Outputs a raw JSON output
`
Logs the user in
`bash`
webtaskify login
> Enter your WebTask account name: mgonto
> Enter your WebTask Token (hidden):
#### Create the proxy files for all tasks inside the /tasks/ folder
`bash`
webtaskify create -f ./tasks/*/.js
#### Create the proxy files for email.js and outputs the proxies into the build/ folder
`bash`
webtaskify create -f ./email.js -o build/
#### Create the proxy files with a baseUrl from Github Pages (Where the code will be deployed)
`bash`
webtaskify create -f ./tasks/*/.js -b 'http://auth0.github.io/taskd-sample/'
#### Log the output of running the WebTask
`bash`
webtaskify logs
Just clone the repo, do npm i` and start hacking :D.
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
MIT