Version: 1.9.8
Platform: x86_64
First, install or update to the latest system software.
sudo apt-get update
sudo apt-get install build-essential chrpath libssl-dev libxft-dev
Leaderboard Using Redis | |
http://labs.strava.com/blog/koms-powered-by-redis/ | |
Strava KOMS, Powered by Redis | |
---------------- | |
http://aimeeault.com/2014/06/22/making-the-most-of-redis-and-sorted-sets/ | |
For example, what if I only want to see a leaderboard of members who are between the ages of 18 and 49? The Sorted Set contains no information on how old each member is. And I don’t want to maintain a separate Redis Sorted Set for just these users, because that’s kind of redundant, right? You probably don’t want to fetch every single one of the potentially hundreds of thousands of records and filter individually… that’s not very efficient! There’s a couple of ways you could approach this with Redis. One is by way of Lua scripting with use of EVAL (which runs Lua) and ZSCAN (which can be used for matching keys and values by rules, similar to regular expressions). |
#!/usr/bin/env ruby | |
require 'syslog' | |
require 'net/http' | |
require 'aws-sdk' | |
Syslog.open | |
AWS.config({ | |
:access_key_id => '<iam user key>', | |
:secret_access_key => '<iam user secret>' |
Scalr | |
http://highscalability.com/blog/2010/3/22/7-secrets-to-successfully-scaling-with-scalr-on-amazon-by-se.html | |
http://stackoverflow.com/questions/10061843/how-to-convert-linux-cron-jobs-to-the-amazon-way | |
Cron Jobs Are Hard To Distribute | |
Watch out when scaling out instances with cron jobs on them. Cron jobs aren't designed for the cloud. If the machine image holding your cron job scales out to 20 instances, your cron job will be executed 20 times more often. | |
This is fine if the scope of your cron job is limited to the instance itself, but if the scope is larger, the above becomes a serious problem. And if you single out a machine to run those cron jobs, you run the risk of not having it executed if that machine goes down. |
<?php | |
session_start(); | |
include_once "google-api-php-client/examples/templates/base.php"; | |
/************************************************ | |
Make an API request authenticated with a service | |
account. | |
************************************************/ | |
require_once realpath(dirname(__FILE__) . '/google-api-php-client/src/Google/autoload.php'); |
<?php | |
// WARNING: right now, support for redis-cluster is experimental, | |
// unoptimized and in its very early stages of development. To | |
// play with it you must have a correct setup of redis-cluster | |
// running (oh hai mr. obvious) and Predis v0.7-dev fetched from | |
// the redis_cluster branch of the Git repository. | |
require 'autoload.php'; |
{ | |
"folders": [{ | |
"follow_symlinks": true, | |
"path": "." | |
}], | |
"settings": { | |
"detect_indentation": false, | |
"ensure_newline_at_eof_on_save": true, | |
"tab_size": 2, | |
"file_exclude_patterns": [ |
<?php | |
// Use in the "Post-Receive URLs" section of your GitHub repo. | |
if ( $_POST['payload'] ) { | |
shell_exec( 'cd /srv/www/git-repo/ && git reset --hard HEAD && git pull' ); | |
} | |
?>hi |
Posted March 06, 2013 02:31 By Veezus Kreist (http://blog.veez.us/)
I've always been a pretty austere guy. I'd rather have less things than more: every time I move I throw out half of what I have. I'm not big into customization, either; if there's a non-ridiculous default, that's what I'm using.
That ethos extends into my work. I use the default Terminal.app on my MacBook, with the built-in Pro theme. I use exactly 12 vim plugins, including my favorite color scheme. My dot files amount to only 300-some lines, including vim options, bash options, git options, and comments.
That's the background for this post on single-session development, the way I've been developing lately. When I say session, I mean shell session. I mean, log into one shell on my laptop, maximize it, and run everything in that one session: no tabs, no screen
, and certainly no tmux
. Bernerd Schaefer started me down this path in his Laptop-Driven Development; that post has been hanging out in the back of my
Launch the instance and connect with ssh.
##Update the server
sudo yum update
##Install php and MySQL packages