Example:
dev
bin
config
data
logs
Gather requirements into new issue | |
POC jade+angular+react | |
i18next | |
fluent | |
custom | |
Selective roll out in templates | |
Translations service |
webpackJsonp([0],[ | |
/* 0 */ | |
/***/ function(module, exports, __webpack_require__) { | |
/** | |
* Test entry file | |
* | |
* This is programatically created and updated, do not modify | |
* |
#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 |
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; |
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. |
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. |
class Something { | |
constructor() => this.calls = 0; | |
totalCalls() => ++this.calls; | |
} | |
let something = new Something(); | |
something.totalCalls(); // 1 |
<?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 |