Skip to content

Instantly share code, notes, and snippets.

Decentralize and democratize the Web.

Jacky Alciné jalcine

Decentralize and democratize the Web.
Block or report user

Report or block jalcine

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
jalcine / Contract Killer
Created May 22, 2017 — forked from malarkey/Contract Killer
The latest version of my ‘killer contract’ for web designers and developers
View Contract Killer

Contract Killer

The popular open-source contract for web professionals by Stuff & Nonsense

  • Originally published: 23rd December 2008
  • Revised date: March 15th 2016
  • Original post


Raspberry Pi VPN Router

This is a quick-and-dirty guide to setting up a Raspberry Pi as a "router on a stick" to PrivateInternetAccess VPN.


Install Raspbian Jessie (2016-05-27-raspbian-jessie.img) to your Pi's sdcard.

Use the Raspberry Pi Configuration tool or sudo raspi-config to:

jalcine / gist:509b4cc280226eec5c49876106239d29
Created Jan 8, 2017 — forked from mtigas/gist:952344
Mini tutorial for configuring client-side SSL certificates.
View gist:509b4cc280226eec5c49876106239d29

Client-side SSL

For excessively paranoid client authentication.

Using self-signed certificate.

Create a Certificate Authority root (which represents this server)

Organization & Common Name: Some human identifier for this server CA.

openssl genrsa -des3 -out ca.key 4096
openssl req -new -x509 -days 365 -key ca.key -out ca.crt
jalcine /
Created May 2, 2016 — forked from alghanmi/
WPS on OpenWRT -- Enabling Wi-Fi Protected Setup on OpenWRT
## WPS on OpenWRT
## This script enables Wi-Fi Protected Setup on OpenWRT.
## Resources
#Install the full wpad package
opkg update
jalcine / landrush.rst
Created Apr 26, 2016 — forked from neuroticnerd/landrush.rst
Vagrant landrush DNS plugin tips and troubleshooting
View landrush.rst


landrush is an excellent Vagrant plugin if you are trying to develop or test in a multi-machine VM environment. It works by spinning up a small local DNS server and registering the private network IPs of each machine during vagrant up so that they can be accessed via their hostname in both the host machine as well as the other guest machines. A great bonus of using landrush is that the VMs can be defined in separate Vagrantfiles (e.g. if you have separate git repos for building different machines).

useful commands

  • vagrant landrush status - show whether the DNS server
jalcine / nginx.conf
Created Feb 27, 2016 — forked from thoop/nginx.conf
Official nginx.conf for nginx
View nginx.conf
# Change YOUR_TOKEN to your prerender token and uncomment that line if you want to cache urls and view crawl stats
# Change (server_name) to your website url
# Change /path/to/your/root to the correct value
server {
listen 80;
root /path/to/your/root;
index index.html;
jalcine / rnb.erb
Last active Sep 10, 2015 — forked from romainl/rnb.erb
RNB, a Vim colorscheme template
View rnb.erb
# Author: Romain Lafourcade (
# Canonical URL:
# This template is designed to help vimmers create their own colorschemes
# without much effort.
# You will need Ruby to generate your colorscheme but Ruby knowledge is
# not needed at all.
jalcine / controller_spec.rb
Last active Aug 30, 2015 — forked from tonycoco/controller_spec.rb
The Greatest Hits of Rspec Testing: Volume 1
View controller_spec.rb
require "spec_helper"
describe ExampleController do
context "GET #index" do
let(:resources) { FactoryGirl.create_list(:resource) }
before do
get :index
jalcine / gist:f58b19ca73a4bcc074d0
Last active Aug 29, 2015 — forked from hueniverse/gist:7686452
Walmart Mobile node.js Setup
View gist:f58b19ca73a4bcc074d0


We run multiple server processes in two data centers. Each process listens on two ports, one for HTTP and one for HTTPS. HTTPS is terminated by Apache prior to reaching node.js. HTTP goes directly from the client to node.js (through a master load balancer). We do not use clusters. We slice our physical servers into thin virtual machines running SmartOS, each with about 3GB of memory designed for a single node.js process.

Our node.js servers are hapi.js servers using the composer functionality and plugins architecture. We have three sets of plugins loaded: mobile web front end experience (single page app), legacy API reverse proxy, and monitoring.

We also serve original node.js services off another server zone which runs closed source plugins using hapi.


View contracting-rate-info.js
function contractingRateInfo( options ) {
You can’t perform that action at this time.