Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/kevoree/grunt-kevoree

A grunt task to start a kevoree-js runtime in dev-mode within a kevoree-js project
https://github.com/kevoree/grunt-kevoree

Last synced: about 1 month ago
JSON representation

A grunt task to start a kevoree-js runtime in dev-mode within a kevoree-js project

Host: GitHub
URL: https://github.com/kevoree/grunt-kevoree
Owner: kevoree
License: lgpl-3.0
Created: 2015-03-26T13:25:33.000Z (almost 10 years ago)
Default Branch: master
Last Pushed: 2017-05-23T14:49:22.000Z (over 7 years ago)
Last Synced: 2024-11-09T19:17:03.700Z (about 2 months ago)
Language: JavaScript
Size: 60.5 KB
Stars: 0
Watchers: 10
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

README

# grunt-kevoree

> Automatically runs kevoree runtime (works like mvn kev:run plugin)

## Getting Started
This plugin requires Grunt `~0.4.2`

If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

```shell
npm install grunt-kevoree --save-dev
```

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

```js
grunt.loadNpmTasks('grunt-kevoree');
```

## The "kevoree" task

### Overview
In your project's Gruntfile, add a section named `kevoree` to the data object passed into `grunt.initConfig()`.

```js
grunt.initConfig({
// all those options are optional because they are the default behavior
kevoree: {
options: {
runtime: 'latest', // default
node: 'node0', // default
kevscript: 'kevs/main.kevs', // default
modulesPath: '.deploy_units', // default
mergeLocalLibraries: [], // default
logLevel: 'debug' // default
}
}
});
```

> Because each options has a default value, you can just add a `grunt.loadNpmTasks('grunt-kevoree')` without any `kevoree` task configuration in your **Gruntfile.js**, and then do a `grunt kevoree` in a terminal

### Options

#### options.node
Type: `String`
Default value: `'node0'`

A string value that is used to determine the node name of the launched Kevoree runtime platform

#### options.runtime
Type: `String`
Default value: `'latest'`

A string value that is used to determine the runtime version (kevoree-nodejs-runtime version)

#### options.kevscript
Type: `String`
Default value: `'kevs/main.kevs'`

A string value that is used to determine the KevScript model that will be used to bootstrap the platform

#### options.modulesPath
Type: `String`
Default value: `'.deploy_units'`

A string value that is used to determine the modulesPath variable for Kevoree resolver (where resolved modules are going to be installed)

#### options.mergeLocalLibraries
Type: `String`
Default value: `[]`

An array containing the paths to your local Kevoree libraries that are not yet pushed on npm registry nor Kevoree registry
Ex:

```js
kevoree: {
options: {
mergeLocalLibraries: [
'/path/to/kevoree-comp-ticker'
]
}
}
```

> NB: Merged local libraries has to be "installed" (i.e `npm install` must have been run)

#### options.logLevel
Type: `String`
Default value: `'debug'`

### Kevscript

#### kevscript
Type: `String`
Default value: `kevs/main.kevs` **this argument is mandatory, whether from command-line or from Gruntfile.js options**

Path that leads to your KevScript file in order to create the Kevoree model to bootstrap on.
KevScript file can be specified from the command-line (if provided, it will be used instead of the file given in the Gruntfile.js)

```sh
grunt kevoree --kevscript=/path/to/my/model.kevs
```

#### ctxVars
Type: `Object`
Default value: `{}`

If set, `grunt-kevoree` will use the given object as the context variables for the KevScript interpretor.
Example:
```js
options: {
ctxVars: {
'NODE_NAME': 'myNode'
}
}
```
This will allow you to use `%NODE_NAME%` that will be converted to `myNode` within your KevScript files:
```kevs
add %NODE_NAME% : JavascriptNode
add %NODE_NAME%.foo : Ticker
```

### Command-line arguments
#### node
Type: `String`
Default value: `node0`

If set, `grunt-kevoree` will use the given node name to start the Kevoree platform.
This argument overrides the given `node` option in **Gruntfile.js**

```sh
grunt kevoree --node=node1
```

#### kevscript
Type: `String`
Default value: `kevs/main.kevs`

If set, `grunt-kevoree` will use the given filepath to load the KevScript model.
This argument overrides the given `kevscript` option in **Gruntfile.js**

```sh
grunt kevoree --kevscript=/path/to/my/model.kevs
```

#### runtime
Type: `String`
Default value: `latest`

If set, `grunt-kevoree` will install the specified `kevoree-nodejs-runtime` version to run the Kevoree platform.
This argument overrides the given `runtime` option in **Gruntfile.js**

```sh
grunt kevoree --runtime=5.1.0
```

### Kevoree Browser Runtime - DevMode
#### options.browserDevMode
Type: `Boolean`
Default value: `false`

If set to `true`, `grunt-kevoree` will start to statically serve the given path in `options.mergeLocalLibraries` (+/browser), plus the one specified in `browserDevModeOptions.path`

#### options.browserDevModeOptions
Type: `Object`
Default value: `{ port: 59000, path: './browser' }`

Browser Runtime DevMode options
`port`: port of the static server
`path`: one of the served directory (all `mergeLocalLibraries`/browser paths are added to this server too)

## Contributing
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using [Grunt](http://gruntjs.com/).