portalnetwork / kaizen-cli Goto Github PK

Set config var

Command

kaizen config set --key PROVIDER --value https://mainnet.infura.io 

kaizen blockchains balance will show the balance with the specified address

Command usage

kaizen blockchains balance --blockchain <BLOCKCHAIN> --network <NETWORK> --address <TRANSACTION_HASH>

kaizen faucet can let user get the testnet token from the supported faucet

Command usage

kaizen faucet --name <NAME> --networkId <NETWORK_ID> --address <YOUR_ADDRESS> --amount <AMOUNT>

NOTICE The amount will be a limit

• NKN React component
• NKN Vue component

Display a single config value

Command usage

kaizen config get --key PROVIDER

• IPFS configuration setting locally
• IPFS upload should specify the path which user want to upload
• Ethereum configuration setting locally
• NKN configuration setting locally
• Improve 'kaizen add' command for better user experience

PR #64 , ba1bc1e, 2915e13, 267d0e8

Seems that "kaizen plugin" is useless. Once I type it, there is nothing showing up on the terminal.

This command will install the plugin with specified name from the plugin list

kaizen plugin install <PLUGIN_NAME>

Requirement

Need check the specified kaizen.json and package.json

Checklist

• CI integration

kaizen blockchains txresult will show the transaction receipt with the specified txhash

Command usage

kaizen blockchains txresult --blockchain <BLOCKCHAIN> --network <NETWORK> --txhash <TRANSACTION_HASH>

• kaizen init
• kaizen publish

Show plugin related information

kaizen plugins

Response command and description

kaizen plugins
kaizen plugins:install
kaizen plugins:uninstall
kaizen plugins:list

This command will add configuration to kaizen

kaizen config --key <KEY> --value <VALUE>

In order to support the KAIZEN manager, KAIZEN CLI should have the user authorized mechanism to log in and log out KAIZEN manager.

List all instance host on KAIZEN Platform

Command

kaizen instances list

In order to replace the original boilerplate which dependent on React or Vue that cause codebase hard to maintain and unfriendly use.

The new boilerplate build up without any frameworks or libraries like react, vue, and angular

This issue will be resolved at 4124c19 on PR #64

• README.md
• README_KR.md
• README_ZH.md

Upload project to IPFS or other else

Command usage

kaizen upload ipfs

The error format can be implement like this

  Kaizen Error ---------------------------------------

  Kaizen command "hi" not found. Run "kaizen help" for a list of all available commands.

  Get Support --------------------------------------------
     Bugs:          github.com/PortalNetwork/kaizen-cli/issues

The dependency progress was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

progress is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Describe the bug
The bug occurs when the node version is v9, and if the node version is v8, it can work as normal.

To Reproduce
Steps to reproduce the behavior:

1. $nvm use v9 switch to the v9 version of Node.js.
2. $npm install to install the packages.
3. $npm run start to start the development server.
4. It will stuck at the starting condition forever.

Motivation

Using CLI to create wallet

Command

kaizen blockchains newaccount --blockchain <BLOCKCHAIN> 

Add Bluzelle component with CRUD

This command will uninstall the plugin with specified name from kaizen.json and package.json

kaizen plugin uninstall <PLUGIN_NAME>

Requirement

Need check the specified kaizen.json and package.json

Checklist

• travis-ci

Unset config vars

Command usage

kaizen config unset --key PROVIDER

As KAIZEN CLI is integrating more services and functions, it is necessary to restructure its codebase. This issue is a list of things that has been updated and to be updated.

Below were completed in #43

• deprecate 'kaizen init'.
• deprecate 'kaizen plugin', and replace it with 'kaizen add --package'.
• new Bluzelle integrated library.
• new processing spinner animation

To be updated

• integrate with NOIA sdk
• update document

Motivation

Support ICON development tools, icon-sdk-js

Effect Commands

# Should install icon-sdk-js
kaizen plugins install icon

# Should uninstall icon-sdk-js
kaizen plugins uninstall icon

# Should show the icon on the list
kaizen plugins list 

The dependency inquirer was updated from 6.2.0 to 6.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

inquirer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

kaizen blockchains list will show the list of support blockchains

Command usage

kaizen blockchains list

NOTICE The amount will be a limit

This feature might be helpful to download any KAIZEN example from github

Show all the plugin support by kaizen

kaizen plugin list

support Kaizen manager features

• create a project
• list projects
• project detail
• create an instance, e.g. ethereum, wanchain, or IPFS

Create a kaizen project by using kaizen create

Command usage

kaizen create --template <TEMPLATE> --name <NAME>

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Refactor kaizen react's boilerplate to ensure it can work as expected

Install a github repository by using kaizen install

Command usage

kaizen install --url <GITHUB>

Show contract commands

Command usage

kaizen contracts

Deploy instance to KAIZEN Platform

Command

kaizen instances deploy --protocol <PROTOCOL> --network <NETWORK> --type <SHARED>

Motivation

kaizen blockchains have to specified networkId with integer format, but kaizen instances accept string, network should using a common format.

Effect Commands

kaizen blockchains faucet
kaizen blockchains tx
kaizen blockchains balance
kaizen instances deploy

Deploy contracts through template or local contracts

Command usage

kaizen contracts deploy --template <URL> --private <PRIVATE_KEY>

Reference: https://github.com/PortalNetwork/kaizen-cli/wiki/kaizen-cli

Should show KAIZEN help by typing kaizen in cli