There are two JSON API styles:
The ID style is the easiest to get started with, but requires that your clients be able to guess the URLs for related documents. It also locks your API into a particular URL structure, which may become a problem as your API grows.
The URL style requires less guessing on the client side, and makes clients more resilient to API changes, but is trickier to use with relationships and compound documents.
| { | |
| "1": { | |
| "labels": { | |
| "de": "Factual Orte", | |
| "es": "Lugares Factual", | |
| "en": "Factual Places", | |
| "fr": "Endroits de Factual", | |
| "it": "Luoghi Factual", | |
| "jp": "Factual 場所", | |
| "kr": "Factual 장소", |
| check process redis | |
| start program = "/usr/bin/redis-server /etc/redis/redis.conf" | |
| stop program = "/usr/bin/redis-cli -p 6379 shutdown" | |
| with pidfile /var/run/redis.pid |
== Overview of Datasets ==
The examples in this book use the "Chimpmark" datasets: a set of freely-redistributable datasets, converted to simple standard formats, with traceable provenance and documented schema. They are the same datasets as used in the upcoming Chimpmark Challenge big-data benchmark. The datasets are:
Wikipedia English-language Article Corpus (wikipedia_corpus; 38 GB, 619 million records, 4 billion tokens): the full text of every English-language wikipedia article, in
Wikipedia Pagelink Graph (wikipedia_pagelinks; ) --
Wikipedia Pageview Stats (wikipedia_pageviews; 2.3 TB, about 250 billion records (FIXME: verify num records)) -- hour-by-hour pageview
| This playbook has been removed as it is now very outdated. |
| require 'rubygems' | |
| require 'chef/encrypted_data_bag_item' | |
| secret = Chef::EncryptedDataBagItem.load_secret('data_bag_key') | |
| data = {"id" => "mysql", "root" => "some secret password"} | |
| encrypted_data = Chef::EncryptedDataBagItem.encrypt_data_bag_item(data, secret) | |
| FileUtils.mkpath('data_bags/passwords') | |
| File.open('data_bags/passwords/mysql.json', 'w') do |f| | |
| f.print encrypted_data.to_json |
| #!/usr/bin/env sh | |
| ## | |
| # This is script with usefull tips taken from: | |
| # https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
| # | |
| # install it: | |
| # curl -sL https://raw.github.com/gist/2108403/hack.sh | sh | |
| # |
| # MOTIVATION: As rails apps are growing, people are noticing the drawbacks | |
| # of the ActiveRecord pattern. Several apps I have seen, and several | |
| # developers I have spoken to are looking towards other patterns for object | |
| # persistence. The major drawback with ActiveRecord is that the notion | |
| # of the domain object is conflated with what it means to store/retrieve | |
| # it in any given format (like sql, json, key/value, etc). | |
| # | |
| # This is an attempt to codify the Repository pattern in a way that would | |
| # feel comfortable to beginner and seasoned Ruby developers alike. | |
| # |
| #!/bin/bash | |
| ES='http://localhost:9200' | |
| ESIDX='test3' | |
| ESTYPE='test' | |
| curl -XDELETE $ES/$ESIDX | |
| curl -XPUT $ES/$ESIDX/ -d '{ | |
| "settings" : { |
This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.
You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.
