mikekelly

{
  "_links":{
    "self":{
      "href":"/users"
    }
  },
  "_forms":{
    "create-user":{
      "title":"Create a new widget",
      "description":"Enter your widget info and submit to create a new widget",

runlevel5

#!/usr/bin/env bash

# Simple move this file into your Rails `script` folder. Also make sure you `chmod +x puma.sh`.
# Please modify the CONSTANT variables to fit your configurations.

# The script will start with config set by $PUMA_CONFIG_FILE by default

PUMA_CONFIG_FILE=config/puma.rb
PUMA_PID_FILE=tmp/pids/puma.pid
PUMA_SOCKET=tmp/sockets/puma.sock

DavyLandman

var net = require('net');

net.createServer(httpsSshSwitch).listen(443);

// if the first byte is 22, it is a https handshake, 
// so redirect it to the actual https server (running on port 8443)
// else redirect it to the ssh instance.
//
// some ssh clients wait for the server to send the first welcome message
// so if we have not seen any data for 2 seconds, assume it is a ssh connection

smeggingsmegger

package main

import (
    "fmt"
    "os/exec"
)

type TunnelParams struct {
    pem_key    string
    ssh_host   string

jpillora

// A small SSH daemon providing bash sessions
//
// Server:
// cd my/new/dir/
// #generate server keypair
// ssh-keygen -t rsa
// go get -v .
// go run sshd.go
//
// Client:

xrstf

Let's Encrypt on Ubuntu 14.04, nginx with webroot auth

This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.

As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).

Configuration

For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:

jcushman

-- Enable pl/v8:
CREATE EXTENSION plv8;

-- Create json history table:
CREATE TABLE json_history (id BIGSERIAL PRIMARY KEY, tstamp timestamp DEFAULT now(), table_name text, column_name text, target_id bigint, transform json);

-- Create test table:
CREATE TABLE test_json (id BIGSERIAL PRIMARY KEY, data JSON);

-- Enable history tracking on test_json.data:

lpil

require 'result/ok'
require 'result/error'

#
# A generic representation of success and failure.
#
# Styled after the Result monad of Elm and Rust
# (or the Either monad of Haskell).
#
# The `#and_then` method can be used to chain functions that

mottalrd

module Commands
  module Meeting
    AcceptSchema = Dry::Validation.Schema do
      required(:user_id).filled
      required(:status).value(eql?: :scheduled)
    end

    class Accept < Command
      def call
        return validate if validate.failure?

croaky

A few lines of Ruby with pg driver is a simple alternative to a job queuing library. Job queues are defined as database tables and workers are defined in one Ruby file.

queuea: bundle exec ruby queue/a.rb
queueb: bundle exec ruby queue/b.rb