cleverstack-cli
Advanced tools
A command line interface (CLI) for the CleverStack ecosystem.
npm install cleverstack-cli -g
Initializing a new project will download and grab CleverStack's cleverstack-angular-seed and cleverstack-node-seed seeds. After initializing the project, cleverstack-cli will automatically install any depedencies that are required through NPM and Bower.
$: clever init my-new-project
You will be asked for database credentials, this is due to the fact that we currently run grunt db after the initialization. This will soon change, and your database credentials will only be asked for when you install a module that requires it.
This will create a new directory called my-new-project with two folders: backend and frontend.
$: cd my-new-project && tree -d -L 1
.
├── backend
└── frontend
2 directories
When installing a module, CleverStack will automatically detect:
The command is:
$: clever install <modules>
Where modules can be:
$: clever install background-tasks
This will install clever-background-tasks within the backend/modules folder.
When removing a module, CleverStack will:
Note: The module name must be the exact name as indicated within the folder
$: clever remove clever-background-tasks
To ensure that everything is working correctly, you can run tests with:
$: clever test
CleverStack will run grunt test within each seed.
$: clever server
There are three commands to be aware of when building a module:
Generate will create a template of a specific component (controller, services, model, tasks, or tests) within module's name that's residing in your current working directory.
$: tree -d -L 1
.
0 directories
$: clever g model my-new-model
$: tree . -d -L 1
.
└── my-new-model
1 directory
$: cd my-new-model && tree . -L 1
.
└── models
1 directory, 0 files
$: tree ./models
./models
├── odm
│ └── MyNewModelModel.js
└── orm
└── MyNewModelModel.js
2 directories, 2 files
Scaffolding is similar to generate except it'll generate every component's template for you.
Note: These files will be generated within your current working directory.
$: tree -d -L 1
.
0 directories
$: clever s my-new-module
$: tree . -d -L 1
.
└── my-new-module
$: tree ./my-new-module -L 3
./my-new-module
├── config
│ └── default.json
├── controllers
│ └── MyNewModuleController.js
├── models
│ ├── odm
│ │ └── MyNewModuleModel.js
│ └── orm
│ └── MyNewModuleModel.js
├── schema
│ └── seedData.json
├── services
│ └── MyNewModuleService.js
├── tasks
│ └── MyNewModuleTask.js
└── tests
├── integration
│ └── MyNewModuleTest.js
└── unit
└── MyNewModuleTest.js
11 directories, 9 files
The new command is similar to scaffold except it'll create the module within the application's module folder.
$: tree ./modules -d -L 1
./modules
└── my-new-module
1 directory
$: tree ./modules/my-new-module -L 3
./modules/my-new-module
├── config
│ └── default.json
├── controllers
│ └── MyNewModuleController.js
├── models
│ ├── odm
│ │ └── MyNewModuleModel.js
│ └── orm
│ └── MyNewModuleModel.js
├── schema
│ └── seedData.json
├── services
│ └── MyNewModuleService.js
├── tasks
│ └── MyNewModuleTask.js
└── tests
├── integration
│ └── MyNewModuleTest.js
└── unit
└── MyNewModuleTest.js
11 directories, 9 files
In order to interact with your environment's models directly, simply type in:
$: clever repl
$: clever help
Usage: clever <command> [options]
Options:
-h, --help output usage information
-V, --version output the version number
Commands:
downgrade [-v version] [-p path] - Downgrades a CleverStack implementation
help - Displays this help message
init <project> [backend|frontend] - Initialized a new project
generate <option> <name> - Generates a controller, service, model, etc. individually
repl - Starts the CleverStack REPL
scaffold <name> - Generates a controller, service, model, etc.
search [query] - Searches for a cleverstack module
server - Starts the CleverStack server
test - Runs tests within your CleverStack environment
upgrade [-v version] [-p path] - Upgrades a CleverStack implementation
Downgrades to the next version (or specified version) of the seed/module (depending on what directory that you're currently in).
Note: This command must run under project's root directory (where frontend and backend are).
$: clever downgrade -h
Usage: clever-downgrade [options]
Options:
-h, --help output usage information
-V, --version output the version number
-v, --versions [version] Downgrade to a specific package version.
-p, --path <path> Path to the package/module.
Examples:
clever downgrade
clever downgrade backend
clever downgrade frontend
$: clever generate -h
Usage: clever-generate [options] [command]
Commands:
service <name> Generates a service as <name> within $PWD/services
services <names> Generates services specified with <name ...> within $PWD/services
controller <name> Generates a controller as <name> within $PWD/controllers
controllers <names> Generates controllers specified with <name ...> within $PWD/controllers
model <name> Generates a model as <name> within $PWD/models
models <names> Generates models specified with <name ...> within $PWD/models
task <name> Generates a task as <name> within $PWD/tasks
tasks <names> Generates tasks specified with <name ...> within $PWD/tasks
test [options] <name> Generates a test t as <name> within $PWD/tests
tests [options] <names> Generates test specified with <name ...> within $PWD/tests
Options:
-h, --help output usage information
-V, --version output the version number
Example:
clever generate model users
clever generate controller users
clever g controller users
clever g controllers users auth email
$: clever init -h
Usage: clever-init [options] [command]
Commands:
<project> Creates a project named <project>
Options:
-h, --help output usage information
-V, --version output the version number
-v, --versions Select a specific cleverstack version that you want initialize with.
-f, --fetch Installs the package without cloning the git repo.
Examples:
clever init my-project
clever init project-frontend frontend
clever init my-project-everything backend frontend
clever init --fetch my-project-frontend frontend
clever init --fetch my-project-backend backend
Lists all modules available for CleverStack.
$: clever list -h
Usage: clever-list [options]
Options:
-h, --help output usage information
-V, --version output the version number
Example:
clever list
$: clever new -h
Usage: clever-new [options] <name>
Options:
-h, --help output usage information
-V, --version output the version number
--no-service Disables generating a service.
--no-controller Disables generating a controller.
--no-model Disables generating a model.
--no-task Disables generating a task.
--no-test Disables generating a test.
Example:
clever new my_module
clever new myModule
Removes a module from the project.
$: clever remove -h
Usage: clever-remove [options] [modules ...]
Options:
-h, --help output usage information
-V, --version output the version number
Examples:
clever remove clever-background-tasks
clever remove auth clever-background-tasks
Creates a REPL instance within your project's environment. Useful for executing ORM/Model commands.
Note: You must set the NODE_ENV environment variable.
$: NODE_ENV=local clever repl
Scanning for seed locations...
Welcome to CleverStack version 0.0.2
Type .commands or .help for a list of commands
cleverstack::local> .commands
.commands Lists all of the REPL commands
.help Alias for .commands
.h Alias for .commands
.modules List all of the modules within this project
.models Lists all models
.exit Exits the CleverStack REPL
.quit Alias for .exit
.q Alias for .exit
.history Show command history
cleverstack::local> .quit
$: clever scaffold -h
Usage: clever-scaffold [options] <name>
Options:
-h, --help output usage information
-V, --version output the version number
--no-service Disables generating a service.
--no-controller Disables generating a controller.
--no-model Disables generating a model.
--no-task Disables generating a task.
--no-test Disables generating a test.
Note:
Scaffold will generate templates within $PWD
If you wish to generate an entire model use clever new <name>
Example:
clever scaffold my_component
clever scaffold myComponent
$: clever search -h
Usage: clever-search [options]
Options:
-h, --help output usage information
-V, --version output the version number
Examples:
clever search users
clever search users auth email
$: clever server -h
Usage: clever-server [options]
Options:
-h, --help output usage information
-V, --version output the version number
-x, --host [host] Set the host for grunt server
-p, --port [port] Set the port for grunt server
Example:
clever server
clever --host 10.0.0.0 server
clever --port 7777 server
$: clever test -h
Usage: clever-test [options] [command]
Commands:
e2e Runs e2e tests
unit Runs unit tests
coverage Generates unit test coverage reports.
Options:
-h, --help output usage information
-V, --version output the version number
Examples:
clever test
clever test coverage
clever test e2e
clever test unit
$: clever upgrade -h
Usage: clever-upgrade [options]
Options:
-h, --help output usage information
-V, --version output the version number
-v, --versions [version] Upgrade to a specific package version.
-p, --path <path> Path to the package/module.
Examples:
clever upgrade
clever upgrade backend
clever upgrade frontend
An online Wiki which can provide support for install, configurations and troubleshooting.
FAQs
Command line interface for CleverStack
The npm package cleverstack-cli receives a total of 22 weekly downloads. As such, cleverstack-cli popularity was classified as not popular.
We found that cleverstack-cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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
Newly introduced telemetry in devenv 1.4 sparked a backlash over privacy concerns, leading to the removal of its AI-powered feature after strong community pushback.
Security News
TC39 met in Seattle and advanced 9 JavaScript proposals, including three to Stage 4, introducing new features and enhancements for a future ECMAScript release.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.