tdooner

{
    elevators: [],
    floorsWaitingUp: [],
    floorsWaitingDown: [],
        
    registerElevator: function(elevator) {
        elevator.i = this.elevators.length;
        
        elevator.log = function(msg) {
            if (this.i !== 0) { return; }

tdooner

diff --git a/webpack.config.js b/webpack.config.js
index ff2c436..b779dbc 100644
--- a/webpack.config.js
+++ b/webpack.config.js
@@ -1,6 +1,7 @@
 /* global __dirname:false */
 
-var webpack = require('webpack');
+var webpack = require('webpack'),
+    exec = require('child_process').exec;

tdooner

require 'redis'
require 'redis-sentinel'
require 'timeout'
require 'logger'

class TestClient
  def initialize
    @sentinels = [
      { host: 'sentinel01.example.com', port: 26379 },
      { host: 'sentinel02.example.com', port: 26379 },

tdooner

# config/initializers/sidekiq.rb
Sidekiq.configure_client do |config|    # and repeat this inside a Sidekiq.configure_server
  config.redis = {
    master_name: 'your-master-name',
    sentinels: [
      "sentinel://sentinel01.example.com:26379",
      "sentinel://sentinel02.example.com:26379",
      "sentinel://sentinel03.example.com:26379",
    ],
    failover_reconnect_timeout: 20,      # roughly 3-5 seconds longer than the sentinel failover-timeout

tdooner

Terminal Multiplexing and YOU!

Screen gives you a terminal which can persist after your SSH connection has closed.

Reasons to use a terminal multiplexer:

• Run a lengthy program (crunching, or a Minecraft server, etc.) even after you disconnect.
• Allows you to resume working exactly where you left off, after your connection breaks or you switch computers.