nk952777

events {
	# nginx requires this section even when applying all default values
	}
http {
	# Upstream keyword is followed by a url (domain name/IP).  This reference encapsulates 
	# the list of backend servers defined for a virtual proxy.  When autnenticating 
	# a certificate from a backend server, the upstream url is supplied to the 
	# certificate authentication process instead of the backend server name. See
	# the comments associated with proxy_pass below for a detailed discussion.

nk952777

#!/bin/sh
# -*- coding: utf-8 -*-

IPTABLES=/sbin/iptables
SERVICE=/sbin/service

SSH_PORT=22

$IPTABLES -F                                                        # すべてのチェインの内容を削除
$IPTABLES -P INPUT   ACCEPT                                         # INPUTチェインのポリシーをACCEPTにする

nk952777

How to setup Let's Encrypt for Nginx on Ubuntu 16.04 (including IPv6, HTTP/2 and A+ SLL rating)

There are two main modes to run the Let's Encrypt client (called Certbot):

• Standalone: replaces the webserver to respond to ACME challenges
• Webroot: needs your webserver to serve challenges from a known folder.

Webroot is better because it doesn't need to replace Nginx (to bind to port 80).

In the following, we're setting up mydomain.com. HTML is served from /var/www/mydomain, and challenges are served from /var/www/letsencrypt.

nk952777

#!/bin/bash
# Startup script for etcd
#
# chkconfig: 2345 20 80
# description: Starts and stops etcd

. /etc/init.d/functions

prog="etcd"
ETCD_BIN=$(which etcd 2> /dev/null)

nk952777

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

nk952777

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

nk952777

Install Go and git, Download Etcd from github and build

sudo yum install -y golang git
go version
sudo git clone https://github.com/coreos/etcd
cd etcd
sudo ./build

nk952777

# Start the old vagrant
$ vagrant init centos-7
$ vagrant up

# You should see a message like:
#  Installing Virtualbox Guest Additions 5.0.20 - guest version is unknown

$ vagrant ssh
vagrantup:~$ sudo rpm -Uvh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-6.noarch.rpm
vagrantup:~$ sudo yum -y update

nk952777

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

• URL

  <The URL Structure (path only, no root url)>

• Method:

nk952777

#! /bin/bash

wget --content-disposition ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-8.40.tar.gz
tar -zxvf pcre-8.40.tar.gz

apt-get -y update
apt-get -y install git
apt-get -y install openssl libssl-dev
apt-get -y install build-essential autoconf automake libtool bison re2c