nosql-tutorial 0.1.0

data/lib/public/stylesheets/src/make_background_images.sh

@@ -0,0 +1,11 @@
+#!/bin/bash
+
+convert -size 1x913 xc:'#FEF9F0' a.png
+convert -size 1x22  xc:'#0B030C' -alpha set -channel A -fx '0.61' b.png
+convert a.png b.png  -append -rotate 90 body.png
+rm a.png b.png
+#convert -size 1x913 xc:'#0B030C' -alpha set -channel A -fx '0.61' a.png
+#convert -size 1x22  xc:'#0B030C' -alpha set -channel A -fx '0.61' b.png
+#convert a.png b.png  -append -rotate 90 h1.png
+#rm a.png b.png
+#convert -size 1024x100 xc:'#0B030C' -alpha set -channel A -fx '0.61' h1.png

data/lib/public/stylesheets/uv.css

@@ -0,0 +1,121 @@
+pre.dawn .MetaSeparator {
+   font-weight: bold;
+   background-color: #DCDCDC;
+   color: #19356D;
+}
+pre.dawn .SupportVariable {
+   color: #234A97;
+}
+pre.dawn .Constant {
+   font-weight: bold;
+   color: #811F24;
+}
+pre.dawn .EmbeddedSource {
+   background-color: #829AC2;
+}
+pre.dawn .StringRegexpConstantCharacterEscape {
+   font-weight: bold;
+   color: #811F24;
+}
+pre.dawn .Support {
+   color: #691C97;
+}
+pre.dawn .MarkupList {
+   color: #693A17;
+}
+pre.dawn .Storage {
+   color: #A71D5D;
+   font-style: italic;
+}
+pre.dawn .line-numbers {
+   background-color: #7496CF;
+   color: #000000;
+}
+pre.dawn .StringConstant {
+   font-weight: bold;
+   color: #696969;
+}
+pre.dawn .MarkupUnderline {
+   text-decoration: underline;
+   color: #080808;
+}
+pre.dawn .MarkupHeading {
+   font-weight: bold;
+   color: #19356D;
+}
+pre.dawn .SupportConstant {
+   color: #B4371F;
+}
+pre.dawn .MarkupQuote {
+   background-color: #C5C5C5;
+   color: #0B6125;
+   font-style: italic;
+}
+pre.dawn .StringRegexpSpecial {
+   font-weight: bold;
+   color: #CF5628;
+}
+pre.dawn .InvalidIllegal {
+   background-color: #B52A1D;
+   color: #F8F8F8;
+   font-style: italic;
+}
+pre.dawn .MarkupDeleted {
+   color: #B52A1D;
+}
+pre.dawn .MarkupRaw {
+   background-color: #C5C5C5;
+   color: #234A97;
+}
+pre.dawn .SupportFunction {
+   color: #693A17;
+}
+pre.dawn .PunctuationSeparator {
+   color: #794938;
+}
+pre.dawn .StringRegexp {
+   color: #CF5628;
+}
+pre.dawn .StringEmbeddedSource {
+   background-color: #829AC2;
+   color: #080808;
+}
+pre.dawn .MarkupLink {
+   color: #234A97;
+   font-style: italic;
+}
+pre.dawn .MarkupBold {
+   font-weight: bold;
+   color: #080808;
+}
+pre.dawn .StringVariable {
+   color: #234A97;
+}
+pre.dawn .String {
+   color: #0B6125;
+}
+pre.dawn .Keyword {
+   color: #794938;
+}
+pre.dawn {
+   background-color: #F5F5F5;
+   color: #080808;
+}
+pre.dawn .MarkupItalic {
+   color: #080808;
+   font-style: italic;
+}
+pre.dawn .InvalidDeprecated {
+   font-weight: bold;
+   color: #B52A1D;
+}
+pre.dawn .Variable {
+   color: #234A97;
+}
+pre.dawn .Entity {
+   color: #BF4F24;
+}
+pre.dawn .Comment {
+   color: #5A525F;
+   font-style: italic;
+}

data/lib/views/ar.rdiscount

@@ -0,0 +1,5 @@
+#### {% title "ORM na przykładzie ActiveRecord" %}
+
+# ORM na przykładzie ActiveRecord
+
+TODO

data/lib/views/datamapper.rdiscount

@@ -0,0 +1,43 @@
+#### {% title "Datamapper" %}
+
+# Datamapper: dm-couchdb, …
+
+
+## Instalacja
+
+Instalujemy następujące gemy:
+
+    sudo gem install dm-core dm-more
+    sudo gem install do_sqlite3 do_postgres
+    sudo gem install dm-validations dm-timestamps 
+    sudo gem install dm-aggregates dm-types 
+
+oraz trochę wtyczek. Wszystkie są 
+[opisane tutaj](http://datamapper.org/doku.php?id=docs:more).
+
+
+## Zestawianie połączenia z bazą SQL
+
+SQLite
+
+    :::ruby
+    # baza danych w RAM
+    DataMapper.setup(:default, 'sqlite3::memory:')
+    # baza danych plikiem
+    DataMapper.setup(:default, "sqlite3:///#{Dir.pwd}/test.sqlite")
+
+PostgreSQL
+
+    :::ruby
+    # Postgres 8.2+
+    DataMapper.setup(:default, 'postgres://localhost/test')
+
+**Uwaga**: You may be wondering how to be more specific about your database
+connection. The second argument can be a hash, containing :host,
+:adapter, :database, :username, :password, :socket, etc. These are
+database-specific but this ought to get you going.
+
+
+## Zestawianie połączenia z bazą noSQL
+
+TODO

data/lib/views/layout.rdiscount

@@ -0,0 +1,38 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta http-equiv="content-type" content="text/html; charset=utf-8">
+
+    <%= stylesheet_link_tag "/stylesheets/screen.css", "/stylesheets/uv.css", "/stylesheets/nosql.css" %>
+    <%= stylesheet_link_tag "/stylesheets/print.css", :media => "print" %>
+    <!--[if IE]>
+      <%= stylesheet_link_tag "css/blueprint/ie.css" %>
+    <![endif]-->
+
+    <title><%= "WB_NOSQL" + page_title %></title>
+  </head>
+  <body>
+    <div class="span-21" id="header">
+      <div class="push-1 span-7">
+        <a href="/nosql/"><span id="wb">WB</span>@<span id="tutorial">NOSQL</span></a>
+      </div>
+      <div class="span-13 last">
+        <div class="append-1" id="links">
+          <a href="http://sigma.ug.edu.pl/~wbzyl/">home</a>
+          <a href="http://sigma.ug.edu.pl/~wbzyl/galeria/zakopane/2009-08-28-zawrat/">galeria</a>
+        </div>
+      </div>
+    </div>
+
+    <div class="span-21 container"><!-- showgrid -->
+      <div class="push-1 span-12" id="content">
+      
+        <%= yield %>          
+        
+      </div>
+      <div class="span-8 last">
+      </div>
+    </div>
+
+  </body>
+</html>

data/lib/views/main.rdiscount

@@ -0,0 +1,47 @@
+# Not only SQL – Data Persistence
+
+<blockquote>
+ {%= image_tag "/images/conan_doyle.jpg", :alt => "[Sir Arthur Conan Doyle]" %}
+ <p>
+   I never guess. It is a capital mistake to theorize before one has
+   data. Insensibly one begins to twist facts to suit theories, instead
+   of theories to suit facts.
+ </p>
+ <p class="author">— Sir Arthur Conan Doyle</p>
+</blockquote>
+
+Na początek dwa cytaty.
+
+[L. Carlson, L. Richardson][ruby receptury]:
+Wszyscy chcą pozostawić po sobie coś trwałego. […]
+Każdy program, który piszemy, pozostawia jakiś ślad swojego działania
+(w najprostszym przypadku są to dane wyświetlane na standardowym 
+urządzeniu wyjściowym). Większość bardziej rozbudowanych programów
+idzie o krok dalej: zapisują one – w pliku o określonej strukturze –
+dane stanowiące rezultat jednego uruchomienia, by przy następnym
+uruchomieniu rozpocząć działanie w stanie, w którym zakończyła się
+poprzednia sesja. **Istnieje wiele sposobów takiego
+*utrwalania danych*, zarówno bardzo prostych, jak i wielce
+skomplikowanych.**
+
+[K. Haines][key-value stores part 1]:
+„Applications, whether web apps, simple dynamic websites or command
+line apps, frequently need some sort of persistent data store. As a
+result, databases have become ubiquitous on modern systems, and
+because of this chicken and egg relationship, programmers will often
+habitually reach for a relational database when the project only calls
+for a way to persist data.”
+
+## Notatki do wykładów
+
+1. {%= link_to "Co już było…", "/summary" %}
+1. {%= link_to "Wprowadzenie do języka Ruby", "/ruby-intro" %}
+1. {%= link_to "Serializacja danych", "/serializacja-danych" %}
+1. {%= link_to "Redis datastore", "/redis" %}
+1. {%= link_to "ORM na przykładzie ActiveRecord", "/ar" %}
+1. {%= link_to "Datamapper dla SQL i noSQL", "/datamapper" %}
+1. {%= link_to "MongoDB", "/mongodb" %}
+
+
+[key-value stores part 1]: http://www.engineyard.com/blog/2009/key-value-stores-in-ruby/ "Kirk Haines, Key-Value Stores in Ruby: Part 1"
+[ruby receptury]: http://helion.pl/ksiazki/rubyre.htm "Ruby Receptury, Bazy danych i trwałość obiektów."

data/lib/views/mongodb.rdiscount

@@ -0,0 +1,41 @@
+#### {% title "MongoDB" %}
+
+# [MongoDB] [mongodb]
+
+MongoDB can be thought of as the goodness that erupts when a
+traditional key-value store collides with a relational database
+management system, mixing their essences into something that’s not
+quite either, but rather something novel and fascinating.
+
+MongoDB is written in C++ and offers the following features:
+
+* Collection oriented storage: easy storage of object/JSON-style data
+* Dynamic queries
+* Full index support, including on inner objects and embedded arrays
+* Query profiling
+* Replication and fail-over support
+* Efficient storage of binary data including large objects (e.g. photos and videos)
+* Auto-sharding for cloud-level scalability (currently in alpha)
+
+MongoDB is a document-oriented database.
+
+Zob. też [Ruby driver for MongoDB] [mongodb ruby].  
+
+[MongoDB: A Light in the Darkness!] [mongodb-light]
+
+[MongoDB Example: centralized logging](http://blog.mongodb.org/post/172254834/mongodb-is-fantastic-for-logging)
+
+[MongoDB Blog] [mongodb-blog]
+
+[Getting Started With MongoMapper and Rails](http://railstips.org/2009/7/23/getting-started-with-mongomapper-and-rails)
+
+[MongoMapper Indy.rb Presentation](http://railstips.org/2009/8/19/mongomapper-indy-rb-presentation)
+
+[What If A Key/Value Store Mated With A Relational Database System?](http://railstips.org/2009/6/3/what-if-a-key-value-store-mated-with-a-relational-database-system)
+
+
+[mongodb-light]: http://www.engineyard.com/blog/2009/mongodb-a-light-in-the-darkness-key-value-stores-part-5/ "A Light in the Darkness"
+[mongodb-blog]: http://blog.mongodb.org/ "MongoDB Blog"
+
+[mongodb]: http://www.engineyard.com/blog/2009/mongodb-a-light-in-the-darkness-key-value-stores-part-5/ "A Light in the Darkness"
+[mongodb ruby]: "http://github.com/mongodb/mongo-ruby-driver" "Ruby driver for the 10gen MongoDB"

data/lib/views/redis.rdiscount

@@ -0,0 +1,20 @@
+#### {% title "Redis" %}
+
+# Redis datastore
+
+[To Redis or Not To Redis?] [redis-or-not]
+
+[Redis] [redis] is key/value store:
+
+* which is blazingly fast
+* works best when data set is small enough that it can fit in available RAM
+* it's OK if some recently updated records are lost in a catastrophic failure
+* makes your life would a lot easier whenever you want cheap and easy 
+  set and list operations
+
+Zob. też [Object-Hash Mapping for Redis] [ohm].
+
+
+[redis]: http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/ "Redis or not…"
+[ohm]: "http://ohm.keyvalue.org/" "Object-Hash Mapping for Redis"
+[redis-or-not]: http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/ "Redis orn not…"

data/lib/views/ruby-intro.rdiscount

@@ -0,0 +1,37 @@
+#### {% title "Wprowadzenie do języka Ruby" %}
+
+# Wprowadzenie do języka Ruby
+
+* David Flanagan, Yukihiro Matsumoto. 
+  [Ruby. Programowanie] [ruby]
+* Aleksander Pohl. [Ruby Intro] [apohllo ruby]
+* [Why's (Poignant) Guide to Ruby] [poignant guide]
+* [Mr. Neighborly's Humble Little Ruby Book] [humblelittlerubybook]
+  ([pdf](http://www.humblelittlerubybook.com/book/hlrb.pdf)
+
+
+## Kilka przykładów na początek
+
+TODO
+
+
+## Klasy IO, File, Dir…
+
+[Dokumentacja klasy IO][ruby io].
+
+
+## Gemy: Mail, ActionMailer
+
+TODO: wysyłanie i pobieranie.
+
+
+## Pobieramy dane za pomocą RSS
+
+TODO: repertuar kin w trójmieście.
+
+
+[ruby]: http://helion.pl/ksiazki/rubypr.htm "Ruby. Programowanie"
+[apohllo ruby]: http://www.apohllo.pl/dydaktyka/ruby/intro/ "Ruby Intro"
+[poignant guide]: http://www.ember.co.nz/files/resources/whys-poignant-guide-to-ruby.pdf "Poignant Guide to Ruby"
+[humblelittlerubybook]: http://www.humblelittlerubybook.com/book/html/index.html
+[ruby io]: http://ruby-doc.org/core/classes/IO.html "Class: IO"

data/lib/views/serializacja-danych.rdiscount

@@ -0,0 +1,75 @@
+#### {% title "Serializacja danych" %}
+
+# Serializacja danych
+
+Po kolei: Marshal, PStore, CSV, YAML
+
+
+## Marshall
+
+TODO
+
+
+## PStore datastore
+
+Ruby comes with a simple hash based key-value store called *PStore*.
+If you’ve never used it, it’s definitely worth learning. For simple
+data storage, PStore can be very useful.
+
+[PStore] [pstore] implements a file based persistance mechanism based
+on a Hash. User code can store hierarchies of Ruby objects (values)
+into the data store file by name (keys). An object hierarchy may be
+just a single object.
+
+
+## YAML
+
+Sesja irb:
+
+    :::ruby
+    hash = { :one => 1, :two => 2, :colors => ["red", "green", "blue"] }
+    require 'yaml'
+    puts hash.to_yaml
+    y_hash = hash.to_yaml
+    new_hash = YAML.load(y_hash)
+    new_hash == hash  #=> true
+
+<b>You need a way</b> to automate the storage and retrieval of professional
+and personal contacts (an address book), but you want it to be in
+plain text so that you can edit the entries in a text editor as well
+as alter them <i>programmatically</i>.
+
+
+## Proste bazy danych
+
+You want a simple contact manager, and you need to share the files
+with someone who may not have access to YAML.
+
+### Rozwiązanie
+
+Our hypothetical YAML crisis provides a chance to look at a gdbm-based
+solution. We'll aim for something that's as close as possible to
+the YAML version of the contact manager, and the best way to guarantee
+that closeness is to use a similar test suite.
+
+
+## Stone: Dead-Simple Data Persistence
+
+To może być ciekawe [Dead-Simple Data Persistence] [stone].
+
+For small applications, a database can be overkill for storing your
+data in a consistent and organized manner. Therefore, Stone was built
+to provide plug-and-play data persistence for any application or
+framework. It is fast, and it is easy… therefore it is good.
+
+Instalacja:
+
+    sudo gem install stone
+
+Czy to będzie działać z Sinatrą? Przykład: Fortunka?
+
+
+#### Linki
+
+[stone]: http://stone.rubyforge.org/ "Dead-Simple Data Persistence"
+[pstore]: http://www.ruby-doc.org/stdlib/libdoc/pstore/rdoc/classes/PStore.html "PStore"