Skip to main content
Starts the application from the project root. It reads the app module’s package.json, brings up the Docker services defined in modules/app/docker-compose.yml when present, discovers every spa, microservice, and api module under modules/, and runs them concurrently — api and microservice modules serve their entrypoint with hot reload, while spa modules run their dev server.

​
Usage

ooneex app:start [options]

​
Examples

Run from the project root to start the Docker services and all runnable modules: 
ooneex app:start
Narrow the run to a module type with --api, --microservice, or --spa. A bare flag keeps every module of that type, --<type>=a,b keeps only the named ones, and flags combine to start several types at once. The shared Docker stack still comes up first regardless of the flags. 
ooneex app:start --api                            # only the api modules
ooneex app:start --microservice                   # only the microservice modules
ooneex app:start --spa                            # only the spa modules
ooneex app:start --microservice=billing,payments  # only the named microservices
ooneex app:start --api --spa                       # the api and spa modules together

​
Options

OptionDescriptionDefault
--apiRun only the api modules. Bare flag keeps all of them; --api=a,b keeps the named ones.All module types
--microserviceRun only the microservice modules. Bare flag keeps all of them; --microservice=a,b keeps the named ones.All module types
--spaRun only the spa modules. Bare flag keeps all of them; --spa=a,b keeps the named ones.All module types