reitermarkus

#!/bin/sh

DATABASE_NAME='wordpress'
DATABASE_USER='wordpress'
ROOT_MYSQL_PASSWORD=`dd if=/dev/urandom bs=1 count=32 2>/dev/null | base64 -w 0 | rev | cut -b 2- | rev`
WORDPRESS_MYSQL_PASSWORD=`dd if=/dev/urandom bs=1 count=32 2>/dev/null | base64 -w 0 | rev | cut -b 2- | rev`


# Write Passwords to File.

manjufy

var elastic = require('elasticsearch');

var client = new elastic.Client({ host: 'localhost:9200' });
var index = 'myindex';
var type = 'document';

(function init() {

  Promise.resolve()
    .then(deleteIndex, handleError)

skyzyx

I'm OK; The Bull Is Dead

By Gopal K. Kapur
Published at Computerworld • JUN 21, 2004 6:00 AM PST

Early in my career, when I worked as an engineer, my boss had a process by which the engineering team was expected to report project status. He insisted that we use the following steps, in the specified order:

1. Punch line: The facts; no adjectives, adverbs or modifiers. "Milestone 4 wasn't hit on time, and we didn't start Task 8 as planned." Or, "Received charter approval as planned."

2. Current status: How the punch-line statement affects the project. "Because of the missed milestone, the critical path has been delayed five days."

dmvaldman

Promises as EventEmitters

I was trying to understand JavaScript Promises by using various libraries (bluebird, when, Q) and other async approaches.

I read the spec, some blog posts, and looked through some code. I learned how to

skyzyx

[20XX-XX-XX] Service Name downtime

• This is a blameless Post-mortem.
• We will not focus on the past events as they pertain to "could've", "should've", etc.
• All follow up action items will be assigned to a team/individual before the end of the meeting.
• If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

---

| | |

stekhn

var elastic = require('elasticsearch');

var client = new elastic.Client({ host: 'localhost:9200' });
var index = 'myindex';
var type = 'document';

(function init() {

  Promise.resolve()
    .then(deleteIndex, handleError)

chrismccord

Phoenix 1.4.x to 1.5.0 upgrade instructions

Phoenix 1.5 requires Elixir >= 1.7. Be sure your existing version is up to date by running elixir -v on the command line.

Install the new phx.new project generator

$ mix archive.uninstall phx_new
$ mix archive.install hex phx_new 1.5.0

icebob

"use strict";

const _ = require("lodash");
const chalk = require("chalk");
const Promise = require("bluebird");
const ServiceBroker = require("../src/service-broker");
const { MoleculerError } = require("../src/errors");

// --- SAGA MIDDLEWARE ---
const SagaMiddleware = function() {

tjunghans

Node V8 Option max-old-space-size

Command line

node --help --v8-options | grep -B 1 -A 1 max-old-space
        type: bool  default: false
  --max-old-space-size (max size of the old space (in Mbytes))
        type: size_t  default: 0

mreschke

# This config will host your main [Laravel] GUI application at /, and any additional [Lumen] webservices at /api/v1 and /api/v2...
# This also works perfectly for all static file content in all projects
# This is full of debug comments so you can see how to print debug output to browser! Took me hours to nail this perfect config.

# Example:
# http://example.com - Main Laravel site as usual
# http://example.com/about - Main Laravel site about page as usual
# http://example.com/robots.txt - Main Laravel site static content as usual
# http://example.com/api/v1 - Lumen v1 api default / route
# http://example.com/api/v1/ - Lumen v1 api default / route