Security News
cURL Project and Go Security Teams Reject CVSS as Broken
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
@liteflow/cli
Advanced tools
CLI for liteflow.
$ npm install -g @liteflow/cli
$ liteflow COMMAND
running command...
$ liteflow (-v|--version|version)
@liteflow/cli/3.1.1 darwin-x64 node-v12.18.3
$ liteflow --help [COMMAND]
USAGE
$ liteflow COMMAND
...
liteflow deploy
liteflow dev
liteflow help [COMMAND]
liteflow init PATH
liteflow login
liteflow logout
liteflow service:doc [SERVICE_PATH]
liteflow service:init DIR
liteflow deploy
Deploy an application
USAGE
$ liteflow deploy
OPTIONS
--confirm Confirm the deployment
--project=project Id of your project
See code: src/commands/deploy.ts
liteflow dev
Start a dev environment for your application
USAGE
$ liteflow dev
See code: src/commands/dev.ts
liteflow help [COMMAND]
display help for liteflow
USAGE
$ liteflow help [COMMAND]
ARGUMENTS
COMMAND command to show help for
OPTIONS
--all see all commands in CLI
See code: @oclif/plugin-help
liteflow init PATH
Create a new application
USAGE
$ liteflow init PATH
ARGUMENTS
PATH Path of your application
See code: src/commands/init.ts
liteflow login
Login to your account
USAGE
$ liteflow login
OPTIONS
--email=email
--password=password
See code: src/commands/login.ts
liteflow logout
Logout from your account
USAGE
$ liteflow logout
See code: src/commands/logout.ts
liteflow service:doc [SERVICE_PATH]
Generate documentation for service and print it to stdout
USAGE
$ liteflow service:doc [SERVICE_PATH]
ARGUMENTS
SERVICE_PATH [default: ./] Path of a service
OPTIONS
-s, --save Save to default readme file
See code: src/commands/service/doc.ts
liteflow service:init DIR
Initialize a service from a template
USAGE
$ liteflow service:init DIR
ARGUMENTS
DIR Directory to initialize a service into
OPTIONS
-t, --template=javascript|typescript Specify the template to use
See code: src/commands/service/init.ts
You can create an alias to easily run the local version of the CLI with different env variable.
Add the following line to your ~/.zshrc
or ~/.bashrc
:
alias liteflow-dev="LITEFLOW_API_ENDPOINT=http://localhost:3000 LITEFLOW_ANALYTICS_DISABLED=true /PATH/TO/liteflow-js/packages/cli/bin/run"
Then source the modified file to take it account:
source ~/.zshrc # or: source ~/.bashrc
Use the alias from any path:
liteflow-dev
FAQs
Liteflow CLI
The npm package @liteflow/cli receives a total of 0 weekly downloads. As such, @liteflow/cli popularity was classified as not popular.
We found that @liteflow/cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
Security News
Biden's executive order pushes for AI-driven cybersecurity, software supply chain transparency, and stronger protections for federal and open source systems.