janeczku

#!/bin/bash
# Cloud-config for CoreOS IPXE deployment on Vultr
##################################################
# This cloud-config bootstraps CoreOS on /dev/vda and provisions:
# - private ip-address on eth1
# - etcd on private network
# - fleet on private network
# - basic firewall (docker compatible)
# - SSHd security hardening
##################################################

bethesque

source 'https://rubygems.org'

gem 'pact', '~>1.7.0'

rauschma

//----- The ECMAScript 6 meta object protocol (MOP) implemented in ES5
// This is how getting a property is handled internally.
// Double underscore (__) implies internal operation.

Object.prototype.__Get__ = function (propKey, receiver) {
    receiver = receiver || this;
    var desc = this.__GetOwnProperty__(propKey);
    if (desc === undefined) {
        var parent = this.__GetPrototypeOf__();
        if (parent === null) return undefined;

schneems

Why not set backlog on Heroku?

First read this: https://mikecoutermarsh.com/adjusting-pumas-backlog-for-heroku/

Now we're on the same page. Heroku will re-route bounced requests from your dynos but it assumes when this happens that your entire app is saturated. https://devcenter.heroku.com/articles/http-routing#dyno-connection-behavior. Each connection gets delayed by 5 seconds, so you're automatically being docked 5 seconds per request.

If you're setting your backlog to a low value (i.e. if you'll ever actually ever hit backlog) then you'll be in for pain. When you get a spike of requests from slashdot/reddit/whatever you're telling your dynos that you would rather they failed then returned slow responses. So this does mean that some requests will be served, but all the others will fail.

If your app ever hits your backlog (no matter what value it is) it is an indicator you don't have enough throughput and you need to scale out to more dynos. If you set this to an arbitrarilly low value, that point comes

krisleech

Task Orientated Authorization

Actor <-> Role <-> Task

• Not a CRUD only solution
• Tasks can describe anything
• Roles and/or Policies
• Actors are typically users, but can be any object
• Actors are not polluted with authentication concerns
• Tasks can be added at runtime

PatrickJS

var EventEmitter = require('events').EventEmitter;
var _ = require('lodash');

// Factory shared
var makePerson = function() {
  var person = {};
  EventEmitter.call(person);
  person.wallet = 0;
  _.extend(person, personMethods)
  return person;

krisleech

Guidelines

Be pragmatic, this is a guide.

Value

Engage with Customer / Domain experts

Encourage them to describe their process and root problem.

benstr

Fork & Symlink an Atmosphere Package

If you want to submit a pull request for an Atmosphere package you will first need to

1. On GitHub fork the GitHub repository you want to make changes to.
2. Clone the repository to your local machine with the Terminal.
   • cd into the folder you want the repository saved in and run the git clone command.
   • If you do not know the git clone command we break it down into 3 parts.
   • First part of command is the git clone.

arunoda

# add the email package
meteor add email

pnc

Using OTP's observer (appmon replacement) remotely

$ ssh remote-host "epmd -names"
epmd: up and running on port 4369 with data:
name some_node at port 58769

Note the running on port for epmd itself and the port of the node you're interested in debugging. Reconnect to the remote host with these ports forwarded:

$ ssh -L 4369:localhost:4369 -L 58769:localhost:58769 remote-host