Eduardo Martinez

@jdormit > ...is to make the api route configurable **cli.js** ``` . . . process.env.JUS_API_ENDPOINT_NAME = args.api || args.a || 'api' . . . ``` **routes.js** ``` . . ....

@jdormit Not really **but...** #### ...we are unable to do PR without CI-Travis and Appveyor complaints since the 20th of April because `node-oniguruma` - we should update dependencies accordingly... -...

@zeke > I would also be open to allowing a command-line option to specify the API path. I already have a local branch ready to PR but we are stuck...

Just created an [api-configurable-endpoint](https://github.com/elingerojo/jus/tree/api-configurable-endpoint) branch at my jus fork. - Added an optional CLI argument to specify the API endopoint instead of the default `'/api'` - Dumped Node 4 support...

Hi, @zeke Are you thinking something like this fake README? --- --- #### README.md # contextualizer > Extract all available data from files in a directory to one javascript object...

I think it can be done if we break the contextualize process in two parts. 1- The modular one that create a context where it does just the basic stuff....

## Ideas for 'proof of concept' of the **contextualizer** module #### First steps - does not include **chokidar** (`jus` does) - can process single files, not necessarily arrays of files....

Invitation, great! @zeke, Thanks. --- @all I just finished a small step. I have a branch named ` alpha-file-self-ctx ` in my fork https://github.com/elingerojo/jus.git - There is no more centralized...

> Opening a branch on jus/jus would be slightly more convenient... Will do > Why? It seems there is now a lot of duplicated code. No duplicated code (that I...

> Why? It seems there is now a lot of duplicated code. Re reading your question, now I get it. You are right. It **seems** a lot of "duplicated" because...