TimothyYe

#!/bin/bash
docker run -it --rm --name certbot \
  -v "/etc/letsencrypt:/etc/letsencrypt" \
  -v "/var/lib/letsencrypt:/var/lib/letsencrypt" \
  -v "/data/letsencrypt:/.secrets" \
  -p 80:80 \
  -p 443:443 \
  certbot/dns-cloudflare certonly \
  -d $1

aviflax

{
"Africa/Abidjan":                   "+00:00",
"Africa/Accra":                     "+00:00",
"Africa/Addis_Ababa":               "+03:00",
"Africa/Algiers":                   "+01:00",
"Africa/Asmara":                    "+03:00",
"Africa/Asmera":                    "+03:00",
"Africa/Bamako":                    "+00:00",
"Africa/Bangui":                    "+01:00",
"Africa/Banjul":                    "+00:00",

TimothyYe

package main

import (
	"flag"
	"fmt"
	"log"
	"net"
	"os"
)

isaacs

# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.
#
# Once you're done here, go to
# http://www.gnu.org/software/make/manual/make.html
# to learn SOOOO much more.

krongk

#C:\Sites\tm_wed\lib\omniauth\strategies\weibo.rb
# Updated at: 2014-09-04
# Author: we@wedxt.com

require 'omniauth-oauth2'

module OmniAuth
  module Strategies
    class Weibo < OmniAuth::Strategies::OAuth2
      

tfrisk-old

#!/bin/sh

# Debian has older Erlang package (R15) in official repositories, Elixir requires newer (R17)
wget http://packages.erlang-solutions.com/erlang-solutions_1.0_all.deb
sudo dpkg -i erlang-solutions_1.0_all.deb
sudo apt-get update
sudo apt-get install -y erlang
rm erlang-solutions_1.0_all.deb

# compile Elixir from source

tollmanz

# Install dependencies
# 
# * checkinstall: package the .deb
# * libpcre3, libpcre3-dev: required for HTTP rewrite module
# * zlib1g zlib1g-dbg zlib1g-dev: required for HTTP gzip module
apt-get install checkinstall libpcre3 libpcre3-dev zlib1g zlib1g-dbg zlib1g-dev && \

mkdir -p ~/sources/ && \

# Compile against OpenSSL to enable NPN

hgfischer

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

• Go HTTP standalone (as the control group)
• Nginx proxy to Go HTTP
• Nginx fastcgi to Go TCP FastCGI
• Nginx fastcgi to Go Unix Socket FastCGI

natew

    require 'bundler/capistrano'
    require 'capistrano_colors'
    load 'deploy/assets'

    # ssh forwarding and shell
    set :default_run_options, { :pty => true }
    set :ssh_options, { :forward_agent => true }

    set :scm_verbose, true
    set :scm, :git

niwo

#!/bin/sh
#
# puma - this script starts and stops the puma daemon
#
# chkconfig:    - 85 15
# description:  Description \
#               goes here...
# processname:  puma
# config:       /etc/puma.conf
# pidfile:      /home/stanislaw/apps/micro-apps/puma/puma.pid