santalex

HTML5 Audio Player w/ Responsive Playlist

This is an HTML5 audio player that detects the user agent of your device/browser/OS and applies styling that matches the native audio player. The playlist responds to the width of your screen and features basic UI controls.

Feel free to fork this pen and add your own user agent styles for different browsers, devices and operating systems.

A Pen by Mark Hillard on CodePen.

License.

Install raspbian, set up your users however you would like, so long as you have sudo access on the user you are running this with. You probably want to resize the image so it fills the SD card as well.

Copy this entire gist to your raspberry pi
Do chmod +x step1.sh step2.sh iptables.sh in the gist folder (so that
Run step1.sh a) This script does a few things - it first updates your raspberry pi, then it installs a few needed utilities, then it upgrades the firmware on your raspberry pi

Nginx FastCGI cache

Example /etc/nginx/nginx.conf using FastCGI (e.g. to PHP-FPM) with FastCGI cache enabled. This will capture returned data and persist it to a disk based cache store for a configurable amount of time, great for robust full page caching.

Will need to create a directory to hold cache files, for the example given here that would be:

$ sudo mkdir -p /var/cache/nginxfastcgi
$ chown www-data: /var/cache/nginxfastcgi

Port Forwarding in Mavericks

Since Mavericks stopped using the deprecated ipfw (as of Mountain Lion), we'll be using pf to allow port forwarding.

####1. anchor file Create an anchor file under /etc/pf.anchors/<anchor file> with your redirection rule like:

	git config --global https.proxy http://127.0.0.1:1080

	git config --global https.proxy https://127.0.0.1:1080

	git config --global --unset http.proxy

	git config --global --unset https.proxy


	npm config delete proxy


	error_page 500 /500.html;
	location /500.html{
	return 500 '{"error": {"status_code": 500,"status": "Internal Server Error"}}';
	}

	error_page 502 /502.html;
	location /502.html{
	return 502 '{"error": {"status_code": 502,"status": "Bad Gateway"}}';
	}

	good, 你已经有了一个自己的shadowsocks代理了，现在想要把这个代理公布出去给所有人分享。
	但是没有两个小时，代理就没法使用了，为什么？因为你需要额外注意以下事项（以下步骤需要比较高的linux技能）
	本文只关注于确保shadowsocks服务还“活着”，如果你希望让其跑得更快，请参考
	https://github.com/clowwindy/shadowsocks/wiki/Optimizing-Shadowsocks

	1、 shadowsocks的timeout设置
	超时时间越长，连接被保持得也就越长，导致并发的tcp的连接数也就越多。对于公共代理，这个值应该调整得小一些。推荐60秒。

	2、检查操作系统的各种限制
	对于openvz的vps，特别需要检查一下

	@echo off
	echo.

	:: set the local (dynamic) port for the Socks5 proxy
	set lport=3128

	:: ssh details
	set rport=22
	set username=andrew
	set hostname=myproxy.tld

	-- a quick LUA access script for nginx to check IP addresses against an
	-- `ip_blacklist` set in Redis, and if a match is found send a HTTP 403.
	--
	-- allows for a common blacklist to be shared between a bunch of nginx
	-- web servers using a remote redis instance. lookups are cached for a
	-- configurable period of time.
	--
	-- block an ip:
	-- redis-cli SADD ip_blacklist 10.1.1.1
	-- remove an ip:

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048