In1t CLI
This tool was desinged to initially rely on Mantra CLI for working with meteor apps, but will gradually unplug it entirely.
Why?
The main goal behind creating this tool is to provide a more robust and flexible way to work with Meteor apps only using this tool, for all of your meteor development tasks.
Currently Mantra CLI is limited on it's functionality, and the rest of functionalities that I want to add can't be just forked and PRed, simply because it's a lot more than what was intented to be added inside Mantra CLI.
Automation:
The goal of building this package is automation.
- Automate new project creation.
- Automate adding default/base modules/packages.
- Automate adding default ESLint roles
- Automate git tasks like push, sync, pr, ..etc
- Automate deployment to a VM, docker container, a swarm cluster, or kubernetes.
- Automate your PM2 scripts.
- ... etc
All of the above, while still maintaining ability to configure everything, to the deepest detail if necessary.
Usage:
As of 0.1.3
Usage: in1t [OPTIONS] <command> [ARGS] Options: -n, --name [STRING] Application name -p, --port [NUMBER] Specify app port -db, --database [STRING]Database URL -met, --method STING Method name -col, --collection STINGCollection name -pub, --publication STINGPublication name -h, --help Display help and usage details Commands: new Create new app/method/collection/publication run Run in development mode lint Lint the app using Eslint, create configs
Roadmap:
Release 0.1.3
- Default ESLint roles.
- Default modules.
Release 1.0.0
- Complete server generators handling.
- Default babel configs.
- Client modules/packages for React.
Release 1.1.0
- Git automation.
Release 1.2.0
- PM2 automation.
Release 2.0.0
- Use Redux for app state on the client as a default approach.
- Automate deployments to a single node (VM).
- Support for dumping remote DB to local DB.
- Support for restoring a local DB to a remote DB.
Release X
- Deployments.
- Support for setting up local environment using
docker
, orminikube
.