Contains the repository that the Core domain uses for accessing the runtime domain in an embedded application.


License
MIT
Install
npm install @atlas-engine/core_domain.runtime_repository.embedded@2.3.14-alpha.1

Documentation

Runtime Domain

Introduction

This project contains all APIs and clients that make up the AtlasEngine's Runtime Domain.

Includes the following components:

Setup and Installation

You can use the reinstall.sh script to setup all APIs. It will perform an npm install and npm run build for all APIs and their subpackages.

The project makes use of meta to manage each APIs individual parts.

Install dependencies with minstall

Although the meta NPM plugin provides a shortcut to install the node_modules for every package this involves a lot of overhead, because it starts fresh in every package and executes npm install in it.

A better way to achieve this is by sharing the same node_modules in multiple packages wherever it is possible.

This is achieved through minstall, which is automatically called during post-install.

So you only have to run npm install from the root folder and everything else is handled automatically.

Hint: The reinstall.sh script also makes use of minstall.

Install dependencies without minstall

If you do not want the APIs to share packages, you can use the following command to set them up individually:

meta exec "npm install"

Meta Quick Guide

Execute a command in all the APIs

meta exec "any command"

If the command contains spaces, make sure to wrap it in quotes.

Execute a command in some APIs

Execute a command on every API, except for persistence_api:

meta exec "any command" --exclude persistence_api

Execute a command only on persistence_api:

meta exec "any command" --include-only persistence_api

You can provide multiple arguments to --exclude and --include-only by separating them with ,.

Link all local modules

meta npm link --all
  • Links all modules specified in the .meta-file if they are a dependency to another module specified in the .meta-file