Get Homebrew installed on your mac if you don't already have it
Install highlight. "brew install highlight". (This brings down Lua and Boost as well)
function keepTrying(otherArgs, promise) { | |
promise = promise||new Promise(); | |
// try doing the important thing | |
if(success) { | |
promise.resolve(result); | |
} else { | |
setTimeout(function() { | |
keepTrying(otherArgs, promise); |
Get Homebrew installed on your mac if you don't already have it
Install highlight. "brew install highlight". (This brings down Lua and Boost as well)
#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に感謝したいと思う
# store all solarized files in one place | |
mkdir ~/.solarized | |
cd ~/.solarized | |
# http://www.webupd8.org/2011/04/solarized-must-have-color-paletter-for.html | |
git clone https://github.com/seebi/dircolors-solarized.git | |
eval `dircolors ~/.solarized/dircolors-solarized/dircolors.256dark` | |
ln -s ~/.solarized/dircolors-solarized/dircolors.256dark ~/.dir_colors | |
git clone https://github.com/sigurdga/gnome-terminal-colors-solarized.git |
http { | |
include /etc/nginx/mime.types; | |
default_type application/octet-stream; | |
log_format ltsv 'domain:$host\t' | |
'host:$remote_addr\t' | |
'user:$remote_user\t' | |
'time:$time_local\t' | |
'method:$request_method\t' | |
'path:$request_uri\t' |
- name: Group by Distribution | |
hosts: all | |
tasks: | |
- group_by: key=${ansible_distribution} | |
- name: Set Time Zone | |
hosts: Ubuntu | |
gather_facts: False | |
tasks: | |
- name: Set timezone variables |
# Android | |
platforms/android/assets/www | |
platforms/android/bin/ | |
platforms/android/gen/ | |
platforms/android/res/xml/config.xml | |
# iOS | |
platforms/ios/build/ | |
platforms/ios/CordovaLib/build/ | |
platforms/ios/www |
Note: This was written using elasticsearch 0.9.
Elasticsearch will automatically create an index (with basic settings and mappings) for you if you post a first document:
$ curl -X POST 'http://localhost:9200/thegame/weapons/1' -d \
'{
"_id": 1,
# vim style tmux config | |
# use C-a, since it's on the home row and easier to hit than C-b | |
set-option -g prefix C-a | |
unbind-key C-a | |
bind-key C-a send-prefix | |
set -g base-index 1 | |
# Easy config reload | |
bind-key R source-file ~/.tmux.conf \; display-message "tmux.conf reloaded." |
I've been struggling to come up with a good pattern for handling loading state in Flux (specifically using Fluxxor, though I think this is an issue for any implementation).
When I say "loading state," what I mean is state in a store that tracks:
Here's my first (very simple) pass at this, a store mixin called LoadingStoreMixin.js
: