| #!/usr/bin/env ruby | |
| # 1. Install hunspell | |
| # $ brew install hunspell | |
| # 2. Download a dictionary and install it in a path listed by `hunspell -D` | |
| # $ open http://wiki.services.openoffice.org/wiki/Dictionaries | |
| # 3. Move this file into your repository | |
| # $ mv commit-msg /path/to/repo/.git/hooks |
| require 'digest' | |
| filename = "House.Of.Cards.2013.S02E01.720p.WEB-DL.x264-Sohu.mp4" | |
| f = File.new(filename, "rb") | |
| puts f.stat.inspect | |
| file_size = File.size?(filename) | |
| offset = [] |
| echo "deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main" | sudo tee /etc/apt/sources.list.d/pgdg.list | |
| wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add - | |
| sudo apt-get update | |
| sudo apt-get install postgresql-9.3 postgresql-server-dev-9.3 postgresql-contrib-9.3 -y | |
| sudo su - postgres -c "psql template1 -p 5433 -c 'CREATE EXTENSION IF NOT EXISTS hstore;'" | |
| sudo su - postgres -c "psql template1 -p 5433 -c 'CREATE EXTENSION IF NOT EXISTS \"uuid-ossp\";'" | |
| sudo su - postgres -c "service postgresql stop" | |
| sudo su - postgres -c '/usr/lib/postgresql/9.3/bin/pg_upgrade -b /usr/lib/postgresql/9.1/bin -B /usr/lib/postgresql/9.3/bin -d /var/lib/postgresql/9.1/main/ -D /var/lib/postgresql/9.3/main/ -O "-c config_file=/etc/postgresql/9.3/main/postgresql.conf" -o "-c config_file=/etc/postgresql/9.1/main/postgresql.conf"' | |
| module CarrierWave | |
| module Storage | |
| class Fog | |
| class File | |
| alias :store_without_safety_net :store | |
| def store(new_file) | |
| retries_remaining = 3 | |
| begin | |
| store_without_safety_net(new_file) | |
| rescue Excon::Errors::SocketError => e |
The graphing widget shows graphs using the Rickshaw graphing library. The names of data fields should be (vaguely) familiar if you've used Rickshaw before.
It's recommended that you replace the /assets/javascripts/rickshaw.min.js from your dashboard with the latest from here.
Get EC2 CloudWatch stats and graph them in Dashing.
A Dashing widget for displaying the number of visitors to your website over a specified timeframe, as reported by Google Analytics
A lot of times you are developing a web application on your own laptop or home computer and would like to demo it to the public. Most of those times you are behind a router/firewall and you don't have a public IP address. Instead of configuring routers (often not possible), this solution gives you a public URL that's reverse tunnelled via ssh to your laptop.
Because of the relaxation of the sshd setup, it's best used on a dedicated virtual machine just for this (an Amazon micro instance for example).
| package main | |
| import ( | |
| "bytes" | |
| "exec" | |
| "log" | |
| "os" | |
| ) | |
| // Pipeline strings together the given exec.Cmd commands in a similar fashion |
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:
