epixa

Gather requirements into new issue

POC jade+angular+react
    i18next
    fluent
    custom

Selective roll out in templates

Translations service

epixa

Kibana directory structure

Example:

dev
    bin
    config
    data
 logs

epixa

webpackJsonp([0],[
/* 0 */
/***/ function(module, exports, __webpack_require__) {

	
	/**
	 * Test entry file
	 *
	 * This is programatically created and updated, do not modify
	 *

epixa

#shutdown()
  removes the message listener from the fork
  
#parseIncomingMessage()
  ignores non-arrays
  invokes onMessage for given msg
  
#onMessage()
  when type is WORKER_BROADCAST
    emits broadcast event with data

epixa

var _             = require('lodash');
var Promises      = require('bluebird');
var exec          = require('child_process').exec;
var semver        = require('semver');
var join          = require('path').join;

var ERR_UNKNOWN = 0;
var ERR_DOWNLOAD_FAILED = 1;
var ERR_ALREADY_EXISTS = 2;
var ERR_JAVA_PATH = 3;

epixa

By default, searches against any time-based index pattern that
contains a wildcard will automatically be expanded to query only
the indices that contain data within the currently selected time
range.

Searching against the index pattern <em>logstash-*</em> will
actually query elasticsearch for the specific matching indices
(e.g. <em>logstash-2015.12.21</em>) that fall within the current
time range.

epixa

By default, searches against any time-based index pattern that contains a wildcard will automatically be expanded to query only the indices that contain data within the currently selected time range.

Searching against the index pattern logstash-* will actually query elasticsearch for the specific matching indices (e.g. logstash-2015.12.21) that fall within the current time range. 

epixa

class Something {
  constructor() => this.calls = 0;
  totalCalls() => ++this.calls;
}

let something = new Something();
something.totalCalls(); // 1

epixa

<?php

// A traditional route in slim:
$app->get('/foo/:id', someMiddleware, function($id) use ($app) {
  $app->response->headers->set('x-custom-header', 'foo');
  $app->render('foo.php', ['id' => $id]);
});

// This is a very convenient pattern for small apps that can not only
// declare but also define all routes in a single file, but it has some

epixa

Controller: https://github.com/epixa/scheduled-do/blob/master/app/Controllers/DropletsCtrl.php

Routes: https://github.com/epixa/scheduled-do/blob/master/config/routes.php

Service location: https://github.com/epixa/scheduled-do/blob/master/config/services.php