wate wate

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

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.

% Title % Name % Date

My first slide

List

In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:

http://techcrunch.com/2007/08/11/facebook-source-code-leaked/

It became a big deal:

http://www.techmeme.com/070812/p1#a070812p1

The two files are index.php (the homepage) and search.php (the search page)

#NoSQLデータモデリング技法

原文：NoSQL Data Modeling Techniques « Highly Scalable Blog

I translated this article for study. contact matope[dot]ono[gmail] if any problem.

NoSQLデータベースはスケーラビリティ、パフォーマンス、一貫性といった様々な非機能要件から比較される。NoSQLのこの側面は実践と理論の両面からよく研究されている。ある種の非機能特性はNoSQLを利用する主な動機であり、NoSQLシステムによく適用されるCAP定理がそうであるように分散システムの基本的原則だからだ。一方で、NoSQLデータモデリングはあまり研究されておらず、リレーショナルデータベースに見られるようなシステマティックな理論に欠けている。本稿で、私はデータモデリングの視点からのNoSQLシステムファミリーの短い比較といくつかの共通するモデリングテクニックの要約を解説したい。

本稿をレビューして文法を清書してくれたDaniel Kirkdorfferに感謝したいと思う

	# 公開鍵のIDをコマンド置換 => "$()"を利用することで公開鍵の名で指定する
	# note: コマンド置換部分では、複数ヒット時対策としてダブルクォートで囲んでいる(複数ヒット時は書式エラーにできる)
	# note: -qオプション: 該当リソースのIDのみ出力するオプション
	usacloud server build \
	--name Example01 \
	--os-type centos \
	--password PUT_YOUR_PASSWORD_HERE \
	--ssh-key-mode id \
	--ssh-key-ids "$(usacloud ssh-key read -q your_ssh_key_name)"

	<?php
	/*
	OCP - Opcache Control Panel (aka Zend Optimizer+ Control Panel for PHP)
	Author: _ck_ (with contributions by GK, stasilok)
	Version: 0.1.7
	Free for any kind of use or modification, I am not responsible for anything, please share your improvements

	* revision history
	0.1.7 2015-09-01 regex fix for PHP7 phpinfo
	0.1.6 2013-04-12 moved meta to footer so graphs can be higher and reduce clutter

	<?php

	date_default_timezone_set('UTC');

	error_reporting(-1);
	ini_set('display_errors', true);


	$file = '/Users/chris/Downloads/wordpress-wxr-example.xml';

	body {
	font-family: Helvetica, arial, sans-serif;
	font-size: 14px;
	line-height: 1.6;
	padding-top: 10px;
	padding-bottom: 10px;
	background-color: white;
	padding: 30px; }

	body > *:first-child {