jhollinger

#
# Easiest. If this doesn't work right, try manual.sh
#

docker run --rm -it -p=0.0.0.0:9222:9222 alpeware/chrome-headless-trunk

# Then open local Chrome go to localhost:9222, then to chrome://inspect. From there you can open new tabs and inspect them.

jhollinger

/**
 * Usage: node csp-strict-dynamic.js dist/
 *
 * Replaces all external script tags in index.html with dynamic loaders, calculates their SHA 256 hashes, and adds those
 * hashes as allowed script sources + strict dynamic.
 *
 * Your index.html should contain a meta tag with a CSP policy, and the script-src section should look like this:
 *
 *   script-src $csp-strict-dynamic;
 *

jhollinger

source 'https://rubygems.org'

gem 'activerecord', '~> 5.2', require: 'active_record'
gem 'sqlite3'
gem 'rake'

jhollinger

def fizzbuzz(input)
  input.map do |n|
    fizz = n % 3 == 0 ? 'Fizz' : nil
    buzz = n % 5 == 0 ? 'Buzz' : nil
    if fizz or buzz
      "#{fizz}#{buzz}"
    else
      n.to_s
    end
  end

jhollinger

#!/bin/bash

find $@ -type f -print0 | wc -l --files0-from=-

jhollinger

require 'securerandom'

module Sidekiq
  class CsrfTokenFix
    def initialize(app)
      @app = app
    end

    def call(env)
      request = Rack::Request.new(env)

jhollinger

# Clone the consolo-release app. It, instead of core, will now hold all our release version info,
# as well as all capistrano tasks.
git clone http://git.consolo.lan/consolo/consolo-release
cd consolo-release
bin/setup

# ONLY use this when deploying to sigma until you hear otherwise

# Deploy core to sigma
bundle exec cap core:sigma deploy

jhollinger

require_relative 'libfax'

puts "Sending fax..."
attempts = mock_fax('555-555-5555', "Here's a fax!")
attempts.each_with_index do |status, i|
  case status
  when :sent
    puts "Fax sent!"
    break
  when :busy

jhollinger

require './main'

run API::Root

jhollinger

/*
 * ManagedWebSocket is a thin wrapper around WebSocket that handles automatic reconnecting and re-binding.
 * If the server/network drops the connection, it will keep trying to reconnect. However, you may call
 * "kill" to permanently disconnect on the client side. The native WebSocket object is available as "ws".
 *
 * Use "on" to bind to normal WebSocket events (open, message, error, close), and to the following custom events:
 *  - connecting: Fired when it is attempting to connect or reconnect.
 *  - drop: Fired when the connection has been dropped by the server or network. (fired before "close")
 *  - kill: Fired when you call "kill" on the MWS. (fired before "close")
 *