Saya termasuk orang yang mengembangkan website tanpa pernah membuatnya dari nol. Maksudnya, saya tidak membuat komponen dari website itu secara manual satu demi satu. Mulai dari arsitektur website, komponen modul, file uploader, user access, image manager, dll. Biasanya semua dilakukan dengan menggunakan CMS yang OpenSource, seperti WordPress dan Drupal (jaman dulu juga termasuk PHPNuke). Biasanya memang saya melakukan modifikasi disana – sini agar website ini bisa bekerja sesuai keinginan. Umumnya akhirnya website tersebut akhirnya bisa berjalan sesuai harapan.

Tetapi kemudian datang masalah seperti berikut ini :

1. Website tersebut membutuhkan galery foto dengan fasilitas slideshow.
2. Website tersebut membutuhkan katalog produk.
3. Website tersebut ingin mengimplementasikan fasilitas social network.
4. Website itu ingin menyediakan fasilitas bagi membernya untuk bisa mengupload file MP3. Dan tiap member nantinya bisa mengatur level akses terhadap file MP3 yang dia upload.
5. Website tersebut ingin mempunyai form yang terintegrasi untuk arsip wawancara.
6. dll

Jika saya menggunakan CMS seperti Drupal. Mungkin hal ini masih bisa ditangani dengan ketersediaan modulnya yang sangat banyak. Atau jika memang modulnya belum tersedia, kita bisa membuat sendiri. Selain itu jika kurang puas, kita masih bisa melakukan oprek lebih dalam dengan menggunakan API yang disediakan Drupal. Dengan tujuan agar website ini sesuai dengan apa yang kita inginkan.

Tetapi, hal ini bisa jadi merupakan masalah baru. Tentunya kadangkala hal ini bisa menjadi solusi untuk satu masalah tetapi bukan tidak jarang malah menimbulkan masalah baru. Beberapa skenario yang sering terjadi :

1. Modul untuk CMS tersedia. Tetapi ada bagian yang tidak sesuai, bahkan mungkin ada bagian yang akhirnya malah terasa mengganggu. Misal modul e-commerce dari Drupal menyediakan begitu banyak fasilitas yang pada kenyataannya tidak saya butuhkan. Sedangkan untuk beberapa bagian justru masih belum sesuai harapan. Dan untuk bisa merubah modul ini, kita harus memahami hampir kesuluruhan struktur modul ini. Ditambah pengetahuan tentang API dari Drupal.
2. Terlalu banyak pilihan modul. Misal modul untuk upload gambar di Drupal. Secara default tidak ada. Kita masih bisa menginstal modul tambahan, sehingga nantinya upload gambar di Drupal akan semudah di WordPress. Tetapi ketika sampai di tahap theming, saya menyadari bahwa field untuk gambar hasil upload modul tersebut tidak bisa diakse langsung. Berbeda dengan image yang diupload menggunakan bantuan module Image Field (CCK).
3. Dengan API yang disediakan, kadangkala kita masih membutuhkan pengetahuan tentang API lain. Dan pada akhirnya mau tidak mau saya harus mempelajari banyak API, hanya untuk mengetahui bagian mana dari API ini yang tepat untuk solusi masalah saya.
4. Salah satu hal yang paling sulit adalah merubah alur kerja dari website ini. Misal jika user ingin register, tidaklah langsung ditampilkan ke halaman register, tetapi harus melalui satu halaman polling terlebih dahulu. Untuk bisa mengimplementasikan ini, secara tidak langsung kita harus tahu alur kerja (workflow) dari CMS yang kita gunakan.
5. Butuh field yang custom untuk tiap post (tidak hanya field TITLE dan POST saja). Secara default WordPress menyediakan fasilitas Custom Fields, tetapi penggunaannya masih belum senyaman CCK di Drupal. Untuk itu harus dibuat modul sendiri.
6. dll

Jika memang akhirnya saya ingin menjadi ahli dari CMS tersebut, saya rasa tidak masalah untuk mengikuti solusi yang saya berikan di atas. Tetapi jika saya hanya ingin menggunakan CMS ini sebagai bantuan, sepertinya effort nya terlalu besar.

Bahkan tidak jarang saya merasa, ketika mempelajari semua API, hook, templating, konvensi, dll dari suatu CMS, effortnya mungkin sama besarnya dengan jika saya membangun website tersebut dari nol.

Jadi apakah akhirnya membuat CMS dari nol?

Tidak. Bagi saya tetap tidak. Karena ada beberapa kemudahan di CMS yang tidak saya dapatkan jika saya harus membangun dari nol. Saya harus membangun kerangka / arsitektur dari website tersebut. Dan cukup banyak pula waktu yang tersita untuk membangunnya.

Jadi apa solusinya?

Framework. Bagi saya solusi di tengah – tengahnya adalah framework. Framework menjadi solusi yang tepat jika saya ingin mengembangkan website yang berbasis konten, tetapi dengan beberapa fasilitas yang tidak umum (seperti kasus di atas tadi). Dengan framework yang tepat, saya bisa membuat API saya sendiri, tetap mendapatkan fasilitas templating secara default, fasilitas layering untuk database, dan salah satu yang paling saya sukai adalah fasilitas URL Friendly secara default. Saya tidak tahu apakah semua framework menyediakan fasilitas tersebut, tetapi yang jelas Framework yang saya pakai (CodeIgniter) menggunakannya.

Pilihan framework yang cukup terkenal :

1. Prado – PHP (contoh : website Univertias Indonesia) : Kalau tidak salah ini seperti menjadi ASP.Net pada PHP
2. CodeIgniter – PHP(contoh : OkeZone.com), Jujur saja, saya tahu CodeIgniter dari situs OkeZone ini, dan sampai saat ini paling nyaman menggunakan ini, karena framework ini terdokumentasi dengan baik.
3. Ruby On Rails – Ruby (contoh : SharingFoto.com) : Situs ini diklaim sebagai web aplikasi pertama di Indonesia yang menggunakan Ruby On Rails.
4. CakePHP – PHP (contoh : OwnCafe.com) : Salah seorang yang sangat aktif dalam edukasi CakePHP di Indonesia adalah Sunu Wibirama (alumni Teknik Elektro UGM). Situs lokal cake-php bisa dilihat di idcake.web.id
5. Symfony (PHP), Django (Python), dll

Saya sendiri masih penasaran dan menantikan Mambo CMS versi 5.0 yang akan menggunakan CakePHP sebagai basisnya. Dengan kondisi seperti itu, maka level kustomisasi bisa dilakukan dari tingkat yang paling dasar (langsung menggunakan framework),di lapis tengah (modul), maupun lapis akhir (theming).

Jika ada yang tertarik dengan framework – framework di atas, jangan lupa pahami satu istilah ini : MVC (Model View Controller)

source: http://okto.silaban.net/2008/02/website/menggunakan-cms-atau-framework/

I just found this one – Creating a Live Datagrid

Very neat and works well too… I still have to check out how it works!

REQUIREMENT:

Ruby and RubyGems
Facebooker gem
A Facebook Account
A Facebook Developer Account/Access

Step-1
login to the facebook developers account using

http://developers.facebook.com/get_started.php

Step-2

• In that page just click Go to the Facebook Developer App
• It will ask for Username and Password , enter the username and password and click login
• Now you will be logged in . In that click Set up new application Button
• Now you will be entered in to create app page
• In that enter your application name and check the agree check box and click save changes
• Now you have created a new application now face book will provide application id , api key and secretkey in the basic tab of that page take note of it

Step-3

• Now click the authentication link on that page
• You will be moving to authentication page in that check the facebook page check box and click save change button
• It will be redirect to application page in that click edit setting it will move to application setting page
• Now click the Canvas link
• You will be moving to Canvas page . In taht in canvas page url enter the name of the application and in the canvas call back url enter the application url and click save changes
• Now you have been sucessfully created an application and it will be redirect to My application page in that you will be getting details about the application take note of it
• Now click view application link in that page
• It will take you to the application page which you have craeted
• In that page click more and click add to my page link and add the application to your page

Step-4

• Now type to this url with your api key http://www.facebook.com/login.php?api_key=YOUR_API_KEY ,It will be moved to the application canvas call back url which you have created
• Now type to this url with your api key http://www.facebook.com/code_gen.php?v=1.0&api_key=YOUR_API_KEY ,now you will be redirecting to Save my login info page
• In that click generate to create a toke , This toke is more important for generating the session key this token in one time validity so dont use for any other part in you application except for creating session key
• Now type this in the addressbar http://www.facebook.com/authorize.php?api_key=YOUR_API_KEY&v=1.0&ext_perm=publish_stream ,it will redirecto facebook authorised page in that click allow button this
• will give permission to post in the wall of your face book

Step-5

Now open the comand prompt and check for all the ruby gems installed including facebooker gem and type

require “rubygems”
require “facebooker”
fb_session = Facebooker::Session.create(“apikey”, “secretkey”)
#now you have assigned all the keys to the fb_session object

Step-6

fb_session.post “facebook.auth.getSession”, :auth_token => “token”
Now you have created a session key like this
{“session_key”=>”session key”, “expires”=>”0″, “uid”=>”user id”}

Step-7

Now type this in your comand prompt

fb_session.post(“facebook.stream.publish”, :message => ‘Hai this is test from ROR Team ‘,:session_key => “sessionkey” ,:target_id => “targetted it”)

Now open you face book as normal user and you can able to see the message Hai this is test from ROR Team in the home wall

So We Can sucessfully post in The wall of Face Book From Third party application

————————————————————————————————————————–

Instalar os pacotes do Ubuntu primeiro:

sudo apt-get install ruby ruby-dev rubygems
sudo apt-get install libopenssl-ruby
sudo apt-get install mongrel

Depois instalar os gems

sudo gem install -v=1.2.3 rails
sudo gem install -v=1.2.3 net-ping
sudo gem install -v=2.0.11 net-ssh
sudo gem install -v=2.0.2 net-sftp
sudo gem install ruby-debug
sudo gem install fastercsv

Para instalar os scripts como serviços

sudo update-rc.d mongreld_xxx defaults

Currently in my rails project, solr and act_as_solr is used as the search engine of the app. As act_as_solr’s original author has stopped further development and the google group community seems inactive, I would like to try to look for alternatives.

I tried to switch to sphinx and thinking_sphinx. I downloaded the source of sphinx 0.9.8.1 and built smoothly on my Mac development machine with snow leopard as my MySQL installation is not by Macports, or you can install sphinx directly from Macports. With the guidelines in thinking_sphinx website, everything goes fine. I installed the gem, added some codes in models, ran the rake tasks and I can start to search.

Then I need to deal with CJK support in my search. Parameters charset_table and ngram_char is need to be set in config file to facilitate this function. I found the charset table list in sphinx wiki. For charset_table, I combined the “common” list and “cjk” list, and it is a huge list. I spent sometime to add this list to the RAILS_ROOT/config/sphinx.yml file. The yml parser will throw “line too long” exception if I paste the list in a single line. I have the make the list in multiline, I tried to google around but the samples of other users just don’t work for me – the parser still can’t parse and throw exception. On the other hand, as thinking_sphinx generates a RAILS_ROOT/config/development.sphinx.conf file base on sphinx.yml, I have to make the list in multiline in the conf file too because sphinx cannot handle a too-long-line in conf file also. Finally, here is my current working sphinx.yml:

development:
sql_range_step: 10000000 #handle fixture random id
min_word_len: 1
min_infix_len: 1
ngram_len: 1
enable_star: true
ngram_chars: #...
charset_table: "U+FF10..U+FF19->0..9, ..., 0..9, A..Z->a..z, a..z, \\\n \
U+F900->U+8C48, ..., U+F904->U+6ED1, \\\n \
#...
U+AC00..U+D7A3, ..., U+A000..U+A48C, \\\n \
U+A492..U+A4C6"

Testing

Full width alphanumeric: works, use “ｈａｐｐｙ”, “２００９” can find “happy 2009″

Traditional & Simplified Chinese: works, can search with single character/multi characters/single word/multi words

Korean: works, same as above

Japanese: partially work, sometimes fail to search with single kana character. For example, searching “あ” (a)/ “あい” (ai)/ “あいう” (aiu) cannot find “あいうえお” (aiueo) but search with “あいうえお” works. Searching “バカ” (BAKA) or “め” (me) can find “バカめ” (BAKAme) (Note: sorry for bad words…lol). Furthermore, this link introduces charset table handling mapping of hiragana, katakana and half width katakana, which is useful in Japanese searching.

The Rubyenrails 2009 Conference, held in Amsterdam as previous years, has just finished. What was new, what was hot and what’s in it for the customer?

One of the nice surprises was the increasing number of large(r) companies that are using Ruby on Rails, to name some examples: Tele2, Nedap, Ordina. Adoption of Rails varies from usage in one department to being the strategic platform of choice.

This nicely coincides with  the inspiring talk by Jeremy Kemper who observes that both Ruby and Rails are not hypes anymore but are becoming mainstream.

The real-life example omroep.nl (presentation by Bart Zonneveld and Sjoerd Tieleman) illustrates what Ruby on Rails can do for the web development industry. Within 6 months a small team built both the site itself and a custom CMS that interfaces with an existing image library. If anything, this example shows both the maturity of the platform and the rapid development cycles that can be achieved.

Other presentations addressed performance (Bart ten Brinke) and security (Jonathan Weiss). They gave various practical pointers for building a performing Ruby on Rails site and increasing security to block various types of attacks (XSS, Session Fixation, CSRF, Javascript Hijacking).

Customers usually don’t care much which database is being used, as long as the functionality of the website works as desired. Perhaps this will be different for MongoDB (presentation by Michael Dirolf), a new document-based schema-free database. Letting go of schemas is quite a step for anybody involved in modern relational databases but it opens up a huge potential for flexibility all the way up to the end-user. An administrator wants a new User field for sub-departments? With MongoDB at the back this will be trivial. Sure, such functionality is possible with a relational database as well, but requires quite a bit more work.

Last but not least Jeremy Kemper and Yehuda Katz highlighted the improvements that Rails 3.0 will bring. Many excellent changes are of technical nature and invisible to customers but the speed-up of the framework (up to 10x for collection rendering) and the improved support for encoding and time zones will likely have a noticable effect on the (international) user experience.

What is your take on the advantages Rails 3.0 will bring?

original

Prologue

1. Test your code

Move code from Controller to Model

1. Move finder to named_scope
2. Use model association
3. Use scope access
4. Add model virtual attribute
5. Use model callback
6. Replace complex creation with factory method
7. Move model logic into the model
8. model.collection_model_ids (many-to-many)
9. Nested model forms (one-to-one) – accepts_nested_attribute_for
10. Nested model forms (one-to-many) – accepts_nested_attribute_for

RESTful

1. Overuse route customization – map.resources …
2. Needless deep nesting
3. Do not use default route

Model

1. Keep finder in their own model
2. Love named_scope
3. The Law of Demeter (LoD) – delegate
4. DRY: metaprogramming
5. Extract into Module
6. Extract to composed class – composed_of
7. Use observer

Migration

1. Isolating seed data
2. Always add DB index

Controller

1. Use before_filter
2. DRY controller – InheritedResources

View – “Never logic code in views”

1. Move code to controller
2. Move code to model
3. Move code to helper
4. Replace instance variables with local variables – render :partial => …, :locals =>…
5. Use form builder
6. Organize helper files
7. Learn rails helpers – content_for, yield, pass block parameter in helper

Code Refactoring

1. The book – “Refactoring Ruby Edition”

Follow 10 simple steps in order to use myspace sdk api

1. Remove all your previous gems installed
+ gem uninstall myspace

2. Checkout sample source code

svn checkout http://myspaceid-ruby-sdk.googlecode.com/svn/trunk/ myspacesdk

3. cd myspacesdk/samples/rails/sample
4. Modify config/database.yml accordingly

development:
adapter: mysql
database: sample_development
password: abcd
pool: 5
timeout: 5000

5. Download http://myspaceid-ruby-sdk.googlecode.com/files/myspaceid-sdk-0.1.11.gem
6. gem install –local ~/Desktop/myspaceid-sdk-0.1.11.gem i.e.PATH_TO_GEM
7. Above command supposed to give you following error otherwise skip to step 10

ERROR:  Error installing /home/sandip/Desktop/myspaceid-sdk-0.1.11.gem:
myspaceid-sdk requires ruby-openid (>= 0, runtime)

8. gem install ruby-openid go to step 6
9. ruby script/server
10. Browse http://localhost:3000/

Modelo

Muy bien continuando con el esquema de trabajo de Rails y haciendo referencia al esquema anterior tenemos el primer elemento de nuestra metodología de programación la cual esta basada en CRUD lo cual hace a Create, Read, Update y Delete y ciertamente esta esta aplicada a las acciones básicas de una base de datos pero entonces que hay con esto, pues bueno una gran ventaja que nosotros obtenemos es el hecho de poder la base de datos con código de Ruby y no por el clásico SQL y para lograr esto Rails utiliza el ORM el cual es Object-Relational Mapping, y eso quiere decir que la base de datos va a ser manipulada como un objeto y que a su vez esto lo vamos a poder realizar gracias a código de Ruby que en su momento será traducido por el propio framework a código SQL, con lo cual ganamos una manipulación de la base de datos se hace de una forma mas intuitiva, no se preocupen lo veremos mas claramente en el siguiente Post cuando empecemos a desarrollar nuestro ejercicio.

Ahora bien la manipulación de Vista será en base a la combinación de codigo html + Ruby de hecho actualmente hay una gran diferencia entre las extensiones de los archivos utilizados para las vistas entre Rails 1.2 y Rails 2.0 en el primero la extensión es .rhtml y en el segundo html.erb el cual hace referencia tanto a html como a Ruby, recordemos que una gran ventaja de nuestra aplicación es el hecho de que con Rails podemos integrar de forma directa las librerías mas importantes de Javascript que son Scriptaculos y Prototype, pero recuerden es de suma importancia tener en cuenta que la lógica de esta aplicación la cual estará siendo afectada por el Controlador y en base a a esta suma obtenemos nuestro sistema de trabajo de MVC.

DRY Dont-Repeat-Yourself, esta metodología de programación hace referencia al hecho de no repetir código y bueno mas haya de no repetir código es el hecho de reutilizar el codigo existente, en si esta tecnica hace referencia a la Programación Orientada a Objetos, y es uno de los pilares de Ruby on Rails.

REST Este punto merece un blog por si mismo, en la actualidad las paginas estaticas donde no existe la posiblidad de compartir información ya sea entre los mismo sitios o bien con aplicaciones de escritorio, estan perdiendo un gran punto de crecimiento y REST es una técnica de arquitectura software para sistemas web que te permite comunicar por medio de HTTP y la combinación con XML, ahora bien se define un conjunto pequeño de operaciones, las más importantes son POST, GET, PUT y DELETE. Con frecuencia estas operaciones se equiparan a las operaciones CRUD que se requieren para la persistencia de datos, aunque POST no encaja exactamente en este esquema, en Rails 2.0 veremos que ha tomado una importancía mayor asi como nos ha facilitado el hacer esta forma de arquitectura.

TDD Desarrollo guiado por pruebas, o Test-driven development (TDD) es una práctica de programación que involucra otras dos prácticas: Escribir las pruebas primero (Test First Development) y Refactorización. Para escribir las pruebas generalmente se utilizan las pruebas unitarias. Primeramente se escribe una prueba y se verifica que las pruebas fallen, luego se implementa el código que haga que la prueba pase satisfactoriamente y seguidamente se refactoriza el código escrito, ahora bien esto ya viene integrado con Ruby on Rails, asi que esto nos permite tener un control sobre la calidad de nuestro software ma sin embargo en este Blog utilizaremos otra metodología no solo de pruebas de software sino de programación la cual es BDD y entrare en esta en detalle en un post siguiente.

NOTA: en Post siguientes realizaremos una aplicación de inicio a fin utilizando el codigo correcto.

Rails specifies standard conventions while creating models, controllers, migrations ( database tables ).

Conventions for creating database tables

1. Table name should be plural

2. id field must be primary_key for table.

3. foreign_key  must be like <model_name>_id i.e. post_id, site_id

Conventions for creating models & Controllers

1. Model name must be singular and controller name should be plural.

Although rails have some standard defined, sometimes it becomes quite necessary to map rails models with non- standard database tables.

1. Table mapping

class Review < ActiveRecord::Base

end

2. Set primary key ( other than rails standar ‘id’ primary_key )

class Review < ActiveRecord::Base

end

3. Foreign key association

class Review < ActiveRecord::Base

end

4. Model association ( non-standard model name )

end

There are many ways that can be used to submit sitemap to search engines.

Lets discuss approaches

1. Put sitemap.xml in public folder and you are done.
   Crawlers will find it through url

http://yourdomain.com/sitemap.xml

2. There are many online sites which generates sitemaps for you.
   like http://www.xml-sitemaps.com/
3. Open following urls in browser
   Be sure to add xml sitemap path for your site.
a. Google submit
http://www.google.com/webmasters/tools/ping?sitemap=XML_SITEMAP_PATH
b. Yahoo Submit
   http://search.yahooapis.com/SiteExplorerService/V1/ping?sitemap=XML_SITEMAP_PATH
c. Ask Submithttp://submissions.ask.com/ping?sitemap=XML_SITEMAP_PATH
d. Webmaster submit
   http://webmaster.live.com/ping.aspx?siteMap=XML_SITEMAP_PATH
5. Best practices in rails to submit sitemap is scheduled task (cron job)a. Write a rake task that will generate sitemap in rails public folder and
will submit sitemap.xml file to search engines. ( as mentioned above.)

Got easy  

One can install gem without rdoc using

gem install GEM_NAME –no-ri –no-rdoc

Skip ri rdoc for all gem installation as i haven’t seen anyone using it.

Edit gemrc file
Add following line to it
vi ~/.gemrc
:gem: --no-ri --no-rdoc

Here is my ~/.vimrc file
---
:verbose: true
gem: --no-ri --no-rdoc
:update_sources: true
:sources:
- http://gems.rubyforge.org
- http://gems.github.com
:backtrace: false
:bulk_threshold: 1000
:benchmark: false

That’s it !

While working with many projects that uses different ruby versions and rails versions, one big problem arises that how do we manage all this ?

We know that managing multiple rails versions wont be problem at all.
but what about ruby versions, How one can manage multiple ruby versions. also while upgrading or degrading ruby version, we need to install all gems again including rails.
i know this is a big pain
How we can overcome this headache. meantime there must be some incompatibilities between two different ruby and rails versions.

Yesterday, i did some research and came to know that…

+ ruby 1.8.7 and rails 2.3.3 got quite stability and effectively. we can use it in next developments.
+ Also, after installing ruby 1.9.1 and dependent gems for my project,
and wondering that there are many incompatibilities while installing new gems with ruby 1.9.1

Some of the gems are mysql, ferret, acts_as_ferret, erubies, etc.

Today, while google, i found rvm gem and that seems very nice to manage multiple ruby versions.

Here are some steps explaining how to use it.

# Install rvm gem to manage multiple ruby version
# pre-requisite is that we already have ruby and rubygems installation
1. sudo gem install rvm

# Install rvm for a particular user
# It will also show how to use gem
2. rvm-install

3. Open new shell

# Show all ruby, jruby installations
4. rvm list

# Install ruby
# specify ruby version
5. rvm install RUBY_VERSION_TO_BE_INSTALLED
(rvm install 1.9.1)

# Install jruby
# By default it will install jruby-1.3.1
6. rvm install jruby

# Specify which ruby version to use ?
# Note: Be sure that ruby version is installed
7. rvm use RUBY_VERSION_TO_USE
(rvm use 1.9.1)

#. Default i.e. version before rvm gem installation
8. rvm use default

Sounds, cool

# install mysql if you dont have already installed
sudo apt-get install mysql-server mysql-client libhtml-template-perl mailx dbishell libcompress-zlib-perl mysql-doc-5.0 tinyca

# install ant and jdk
sudo apt-get install ant sun-java6-jdk

# install jruby
mkdir software
cd software
wget http://dist.codehaus.org/jruby/jruby-bin-1.1.5.tar.gz
tar xvfz jruby-bin-1.1.5.tar.gz
ln -s jruby-1.1.5 jruby
export PATH=$PATH:$HOME/software/jruby/bin

# install the version of rails wanted by jruby
jruby -S gem install jruby-openssl
jruby -S gem install rails

# list your gems
jruby -S gem list

# install the gems needed for db
jruby -S gem install activerecord-jdbc-adapter activerecord-jdbcmysql-adapter

# generate some code
cd ~/scripts/ruby
jruby -S rails wherehaveyoubeen -d mysql
cd wherehaveyoubeen
jruby script/generate controller states index

# configure access to the database server
vi config/database.yml

#development:
# adapter: jdbcmysql <- very important!
# encoding: utf8
# database: test_development
# username: root
# password: database
# socket: /var/run/mysqld/mysqld.sock

# generate the db
jruby -S rake db:create:all
jruby -S rake db:migrate

# edit your app
sudo apt-get install emacs ruby-elisp irb1.8 emacs22-el
emacs -bg black -fg wheat app/views/states/index.html.erb

# uncomment the secret in app/controllers/application.rb
vi app/controllers/application.rb

# run your app
jruby script/server

Here are the simple steps to be followed while upgrading rails version to use.

# Install rails version
1. gem install rails -v
== gem install rails 2.3.3

# Upgrade environment.rb for new version
2. RAILS_GEM_VERSION = ” unless defined? RAILS_GEM_VERSION
== RAILS_GEM_VERSION = ‘2.3.3′ unless defined? RAILS_GEM_VERSION

# Upgrade necessary files for the new version
3. rake rails:upadte

# Start server
4. /script/server

Thats, it !

Install passenger program that will run your rails application
1. sudo gem install passenger
Install nginx server with passenger enabled
2. passenger-install-nginx-module

it will open apt, click “Enter” to contine
then select option 1 for default install
then it will ask
Where do you want to install Nginx to?

Please specify a prefix directory [/opt/nginx]:
press enter

then copy following block

server {
listen 80;
server_name www.yourhost.com;
root /somewhere/public;   # <— be sure to point to ‘public’!
passenger_enabled on;
}

Make nginx Configuration
3. vi /opt/nginx/conf/nginx.conf
Make passenger_root and passenger_ruby path to configuration

http {
passenger_root /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.4;
passenger_ruby /usr/local/bin/ruby;

then add server configuration block inside http block
http{
…
server {
listen 80;
server_name www.yourhost.com; //Make sure this dns entry inside /etc/hosts
root /carsonline/public;   # <— be sure to point to ‘public’! //here carsonline is RAILS_ROOT
passenger_enabled on;
}

Thats, all

4. Launch Server

/opt/nginx/sbin/nginx

What is sitemap ?

Sitemap is nothing but a .xml file containing urls available on your site

It contains URL, last modified date, frequency of content change and priority ( between 0..1 )

Why we need sitemap ?

We can submit sitemap file to search engine. It will help them in analysing what urls on your site are available for crawling.

What is xml pattern ?

   <?xml version="1.0" encoding="UTF-8"?>
      <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

        <url>
           <loc>http://www.example.com/</loc>
           <lastmod>2005-01-01</lastmod>
           <changefreq>monthly</changefreq>
           <priority>0.8</priority>
        </url>
       ...
       ...
    </urlset>

What will be the path for sitemap ?

“www.example.com/sitemap.xml”

Are we going to generate sitemap manually ?

No… there is mephisto sitemap plugin.We can use it.

script/plugin install http://svn.appelsiini.net/svn/rails/plugins/mephisto_sitemap/

Am i needed to generate to sitemap for each request ?

No ………..we can generate it in background task daily basis.

How it will be accessed for request to sitemap ?

we can define path to local file in routes.

map.connect “sitemap.xml”, :controller => :sitemap

Class SitemapController

def index

render “some local file path”

end

….

Here are the reference links

http://www.fortytwo.gr/blog/19/Generating-Sitemaps-With-Rails

http://www.bestechvideos.com/2008/07/04/ruby-plus-71-how-to-create-a-seo-sitemap-for-rails-apps

　　
　
　
1. Snow Leopardでのデフォルト環境確認

$ ruby -v
ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
$ gem -v
1.3.1
$ rails -v
Rails 2.2.2

　
2. mysql インストール

http://dev.mysql.com/downloads/mysql/5.1.html#macosx-dmg こちらから Mac OS X 10.5 (x86_64) をダウンロード。ディスクイメージを開いたら、デフォルトのオプションのまま、まず「mysql-5.1.38-osx10.5-x86_64.pkg」をインストール。次に、同じくデフォルトオプションのまま「MySQLStartupItem.pkg」をインストールし、さらに「MySQL.prefPane」をダブルクリック
　
3. mysql 操作

$ /usr/local/mysql/bin/mysql -u root -p
Enter password:

mysql> create database mysqldemo default character set utf8;

mysql> grant all privileges on mysqldemo.* to
    testuser@localhost identified by 'password';

　
4. gem install mysql

$ sudo env ARCHFLAGS="-arch x86_64" gem install mysql --
   --with-mysql-config=/usr/local/mysql/bin/mysql_config

(以下のエラーが発生した場合はXcodeをインストールしてください)

　
5. rails プロジェクト作成

$ rails -d mysql mysqldemo

database.yml ファイル編集

development:
    adapter: mysql
    encoding: utf8
    database: mysqldemo
    pool: 5
    username: testuser
    password: password
    socket: /tmp/mysql.sock

　
6. scaffold 作成

$ script/generate scaffold user email:string name:string age:integer
$ rake db:migrate

　
7. サーバー起動して確認

$ script/server

Leading creative digital agency in London are looking for a junior/mid weight back-end developer. The essence for this role is a good split between PHP and DOT.NET.

Knowledge in the following ========================
* ASP.NET 2.0 & 3.5 (C#)
* PHP 5
* Visual Studio 2008
* Object-Oriented Programming
* SQL Server
* MySql
* Web site security concepts
* XML
* XSLT

Professional Programming Practices such as version control (VSS, Subversion, CVS etc).

Skills in the following will be merited (in no particular order)
========================== ===========

* Agency experience
* Fluorine/AMF
* CMS Systems
* Winforms .net
* Flash – underlying concepts
* Actionscript
* Javascript
* XHTML/CSS
* Disability Discrimination Act (DDA)
* VB.net
* Java
* RubyOnRails
* Experience with other databases
* Knowledge of various PHP frameworks
* Experience in building Social Networking Apps
You have a degree in Computer Science (or equivalent experience) and an understanding and passion of web based software systems and the designing of those systems. You also strive to gain extensive experience in the architecture of large object oriented software projects. You are a skilled programmer who can work independently and yet you have the ability to motivate people and assert your ideas. You will be part of a team and you will have an imperative role in the opening stages of each project.

They want you to be:
Passionate about the Internet
Quality focused in every detail
Precise
Professional
Independent
Communicative
Problem Solver

Excellent opportunity to progress your career for this very creative digital agency.

 neil@majorplayers.co.uk

There are almost 4 to 5 simple steps you need to followed before getting multiple sites working using radiant cms

1. Setup radiant cms

first Install radiant gem
sudo gem install radiant

set ‘radiant’ under path
export PATH=$PATH:/var/lib/gems/1.8/gems/radiant-0.8.0/bin

Now, we have done with radiant installation.

Let’s create new project..

$ radiant multisite -d mysql
$ cd multisite/

Edit database.yml


$ vi config/database.yml
development:
adapter: mysql
database: multisite_development
username: root
password: abcd
host: localhost

Migrations

rake db:create

# Run the database bootstrap rake task:

rake db:bootstrap
This task will destroy any data in the database. Are you sure you want to
continue? [yn] yes
...
Create the admin user (press enter for defaults).
Name (Administrator): admin
Username (admin): admin
Password (radiant):
....
Select a database template:
1. Empty
2. Roasters (a coffee-themed blog or brochure)
3. Simple Blog
4. Styled Blog
[1-4]: 2
....


Now we are ready to start

script/server

Open browser
http://localhost:3000

We will see your site up

To manage site

http://localhost:3000/admin

Now Lets start with multiple sites management
1) Clone multi_site extension into vendor/extensions of your project.
cd vendor/extensions/
git clone git://github.com/zapnap/radiant-multi-site-extension.git multi_site
2) Run the extension migrations.

rake db:migrate:extensions

3) Run the extension update task.

rake radiant:extensions:multi_site:update

4) Restart your server

And we are done with multisite installation

Open

http://localhost:3000/admin/sites

Add multiple sites as you wanted
Name Domain pattern Base domain name
==== ============== ================
site 1 sandip sandip
site 2 gautam gautam

Dont forget to make dns entries
vi /etc/hosts

127.0.0.1 localhost
...
127.0.0.1 sandip
127.0.0.1 gautam

One more, by deault pages created for new sites added are not published.
Please be sure to make them published and modify contents to identify them

Now you can view different sites.

http://sandip:3000

http://gautam:3000

Thats, All

Cheers !

$@ndip

Rails community has released rails 2.3.3 recently with major upgrades and several bug fixes added.

On the other side, Rails 3 ( i.e. merge of rails and merb framework ) is supposed to be officially get released in this May.

Lets see what are the notable features added in rails 2.3.3

1. Rack

What is this rack ?
Abstraction built on the top of rails framework

What it does ?
It provides minimal interface between webservers supporting ruby ( like  apache-mongrel, nginx-passenger ) and rails framework.
Gives access to middleware goodness
i.e. wrapping HTML requests and response in simple way
unifies and distills the API for web servers, web frameworks, and software in between

read more …

2. Metal
It is a subset of rack middleware specially designed to integrate with rails    application.

Why to use it ?
Whenever you need achieve raw speed for certain requests by skipping action controller stack.
read more …

3. Engines
It was a plugin that got merged in rails core.
It is used for sharing controllers, models and views seamlessly from within a plugin to your rails application.
read more …

4. Templates
These are the ruby files which describes which gems, plugins and initiliazers  has to be added while creating new rails project.
read more …

5. Nested Forms
Earlier nested forms for has_one and has_many associations wasn’t
there in rails.
this release added nested forms complex associations in models.
read more … also see …

One of good rails architecture diagram found while google

Rails 2.3 architecture diagram

Edge rails Installation
gem install rails –source http://gems.rubyonrails.org

Thanks to rails community  for bringing this things in rails core.
Cheers, now rails is getting its way !

Quem  já sabe quem sou eu, lê esse blog e vê meus tweets,  talvez saibam que eu sou Pernambucano, isso pra mim é muitas vezes irritante pois não existe uma comunidade ou grupo de desenvolvimento Ruby(Ou qualquer outra coisa). Dizem que o Brasil está quase sempre 2 anos atrás dos States e parece que Pernambuco tá 2 anos atrás do Brasil . Mas ontem a coisa foi diferente, eu nunca tinha visitado uma Universidade até então, só que eu tive a oportunidade de conhecer um amigo de lá, ele cursa Ciência da Computação, a Universidade é a Federal Rural de Pernambuco. Quando eu disse que nunca tinha visitado uma faculdade não foi bem assim, eu tinha ido à uma particular chamada Maurício de Nassau, mas me decepcionei, só vi filhindo-de-papai motherfucker, a alta burguesia recifence em versão pré-adulta, foi péssimo, um dia eu li um post do Fábio Akita que descreveu tudo o que eu senti naquele dia. Mas ontem foi mágico nunca pensei que algo público pudesse ser tão bom (Finalmente algo pra poder elogiar no Brasil) me parece que as Federais são o inverso total do Ensino Básico brasileiro, totally amazing!

Pulando pra parte mais legal já que é impossível descrever tudo…

Eu assisti uma noite de aula inteira de puro aprendizado, uma turma muito centrada e ao mesmo tempo descontraída, o professor era muito bom. A gente viu sobre princípios básicos da Computação, loops, matemática básica: Funções polinomiais, matrizes, cofatores, álgebra linear, álgebra booleana, além de um pouco de Teoria da Computação. Infelizmente eu não posso ir sempre, e só de pensar que eu ainda tô no 2° ano do médio… .  As próximas aulas já vai ter a introdução à programação, linguagens (Eles começam com C e Python). Tinha um cara lá muito maluco de 2 metros de altura que escrevia C++ como Shakespeare escrevia romances (é, eu sei… C++…) Esse cara me ensinou – quase – tudo que eu ainda não sabia sobre o funcionamento de uma CPU, ele me deu um insight indescritível. Lá eu vi, que, pelo menos por enquanto a coisa não é pra Web, esse cara que eu falei antes mal sabe HTML. A primeira professora falou sobre matemática básica e tals , mas as sulas seguintes foram com um Professor chamado Rodrigo (Coincidência?) o cara era muito louco e muito bom professor, ninguém se surpreenderia se ele começasse a explicar Processamento de Gráficos em francês.

E agora…

A estrutura lá é mesmo excepcional, PCs com Ubuntu e XP e internet WIFI de alta velocidade, postei até um tweet enquanto estava lá, no Ubuntu andei fuçando alguns docs e colei 2 no Google Docs. Seriam das próximas aulas:

Link pra um…
Link pra o outro…

Foi mal pessoal não consegui colocar o embed no WordPress.

Evangelizando…

Como não poderia deixar de ser, eu vi a galera escrevendo C++ e tals e resolvi cutucar. Dei uma  ’aula’  breve sobre o que eu sei de Ruby – expliquei a origem e história da linguagem, mostrei a semelhança com Python e Perl, mostrei as gems. Tudo isso sem contar que o Ubuntu ainda não tava com nada de ruby instalado, rodei um sudo apt-get intall ruby1.8.7 depois sudo apt-get install irb e gems, sqlib, etc.. Tudo isso em uma aula! Mostei aos caras o que se pode fazer com Ruby, cheguei a instalar o Rails mas não deu tempo de demonstrar, ainda falei sobre git e os caras ficaram babando, eles só conheciam svn e ficaram impressionados tbm com a praticidade e usabilidade do Github. Pena que não deu pra mostrar Rails, só queria mostrar o scaffolding , pelo menos eles viram como o Ruby é lindo.

Como se não bastasse tudo isso, a galera foi super receptiva comigo e ficou de olho num espinhento de 15 anos, eles gostaram bastante e eu mais ainda. Os caras ficaram abismados pelo fato de eu ser mega-autodidata teve até um lá que perguntou se eu era autista, hiper-ativo ou coisa parecida, QI elevado, wtf? Atacaram a minha vaidade hehe. Pra terminar, conheci altas gatas uma mais linda que a outra, como é pode?!

Valeu galera, valeu Ruby, valeu UFRPE!

Search Engines ( like google, yahoo ) mainly uses crawlers for returning results.

Crawler is the program which searches world wide web ( www ) and returns ranked pages.

Lets see what are the search engine optimization (SEO) techniques we can adopt so that your rails
website pages will appear in search results.

1. Title Of Page

2. Meta tags

3. Page URL

4. Page Contents ( this includes anchors to other pages, headers, image titles and alt texts when image not found then normal texts )

We can easily skip some pages from search by mentioning them in robots.txt which is by default should be in application root.

And Ofcourse, we can manage all this in rails very easily..

How ????

We can have in rails

1. Dynamic page titles,

2. Meta tags and

3. Sexy perma URLs in rails

4. Also, we can define some standard on page content development.

…got Easy ……, Cheers !

$@ndip

Deseaba poner una busqueda a una pequena app en rails, asi llegue al tutorial:
Simple Search de ahi al screencast, pero nada, no funcionaba, a buscar algun tutorial y nada, mare, ajo, erda, mai… Asi q ha usar el metodo “por tonteo y error”.

Primero:
$ ruby script/generate scaffold supplier code:string name:string

Archivos a modificar :
app/model/suppier.rb
app/controllers/suppliers_controller.rb
app/views/suppliers/index.html.erb

1. Insertar un text_field para busqueda:
file: app/views/suppliers/index.html.erb

<h1>Listing suppliers</h1>
<% form_tag request.path, :method => 'get' do %>
<% content_tag :label do %>
Search:
<%= text_field_tag :search, params[:search] %>
<% end %>
<% end %>


2. En el modelo, la parte de busqueda
file: app/model/suppier.rb

class Supplier < ActiveRecord::Base
def self.search(search, page)
Supplier.paginate :page => page, :per_page => 5, :conditions=>['name like ?', search], :order => ‘code desc’
end
end

3. Y finalmente, el controlador
file: app/controllers/suppliers_controller.rb

def index
@search = '%' + params[:search] + '%'
@suppliers = Supplier.search(@search, params[:page])

respond_to do |format|
format.html # index.html.erb
format.xml { render :xml => @suppliers }
end
end

Y ya ta... bueno para la proxima le doy formato al codigo... uff

Esse artigo é uma tradução do Post original do Yehuda katz

Como as pessoas sabem, tem ocorrido um certo vai-e-vem entre mim, o aparente inimigo do alias_method_chain, e as pessoas que vêm alias_method_chain como uma API extremamente razoável.

Existem basicamente 2 formas para usar o alias_method_chain:

#Organizar Código Interno
#Modificar Código que já Existe

Usar o alias_method_chain para organizar código interno é uma discussão interesssante que Eu espero continuar no futuro.  Hoje Eu quero direcionar o seu uso para substituir métodos no ActionController::Base e no ActiveRecord::Base. Pessoas que fazem isso estão cegamente usando a técnica que tem sido mais evangelizada como solução para todos os seus problemas quando Ruby vem com uma solução perfeitamente boa.

Considere esse post do vaporbase, que Eu definitivamente não estou usando. Isso representa uma forma comum que as pessoas estão tentando usar em Rails.

Primeiro, o uso em um Model:

class Foo < ActiveRecord::Base
  include FooBar
end

Segundo, a implementação no código:

module FooBar
  module ClassMethods
    def find_with_bar( *args )
      find_without_bar( *args )
      #...or whatever 
    end
  end

  def self.included(base)
    base.class_eval do
      extend ClassMethods
      class << self
        alias_method_chain :find, :bar
      end
    end
  end
end

Isso equivale a:

module FooBar
  def self.included(base)
    base.extend(ClassMethods)
  end

  module ClassMethods
    def find(*args)
      super
      #...or whatever
    end
  end
end

Assim tá certo, se você está procurando modificar subclasses do ActiveRecord::Base ou ActionController::Base. Lembre-se que você está numa linguagem de programação orientada a objeto com herança.

Se você quiser modificar todos os models em sua aplicação, crie sua própria subclasse no ActiveRecord::Base , e “here” isso através da sua aplicação.

Outro exemplo

Um outro exemplo, de uma pessoa muito inteligente foi ainda mais longe.

Ele começou com:

class Post < ActiveRecord::Base
  class << self
    def find_with_tags(*args)
      options = extract_options_from_args!(args)
      if tag = options.delete(:tags)
        options[:select] ||= 'posts.*'
        options[:joins]  ||= ''
        options[:joins]  << <<-END
          INNER JOIN posts_tags AS inner_posts_tags ON posts.id = inner_posts_tags.post_id
          INNER JOIN tags AS inner_tags ON inner_tags.id = inner_posts_tags.tag_id
        END
        add_to_conditions(options, tags.map { 'inner_tags.name = ?' }.join(' OR '), *tags)
      end
      find_without_tags(*(args + [options]))
    end
    alias_method_chain :find, :tags

    def find_with_query(*args)
      options = extract_options_from_args!(args)
      if query = options.delete(:query)
        if query.empty?
          add_to_conditions(options, 'false')
        else
          term = "%#{query}%"
          add_to_conditions(options, "posts.content LIKE ? OR posts.title LIKE ?", term, term)
        end
      end
      find_without_query(*(args + [options]))
    end
    alias_method_chain :find, :query

    protected

    def add_to_conditions(options, condition, *args)
      condition = args.empty? ? condition : [condition, *args]
      if options[:conditions].nil?
        options[:conditions] = condition
      else
        options[:conditions] = sanitize_sql(options[:conditions]) + " AND (#{sanitize_sql(condition)})"
      end
    end
  end
end

Percebendo que isso não tava muito DRY, ele recorreu à metaprogramação:

class Post < ActiveRecord::Base
  class << self
    def handle_find_option(name, &block)
      eigenclass = class << self; self; end
      eigenclass.send :define_method, "find_with_#{name}_handled" do |*args|
        options = extract_options_from_args!(args)
        if option = options.delete(name)
          block[options, option]
        end
        send("find_without_#{name}_handled", *(args + [options]))
      end
      eigenclass.send :alias_method_chain, :find, "#{name}_handled"
    end
  end
end

class Post < ActiveRecord::Base
  handle_find_option(:tags) do |options, tags|
    options[:select] ||= 'posts.*'
    options[:joins]  ||= ''
    options[:joins]  << <<-END
      INNER JOIN posts_tags AS inner_posts_tags ON posts.id = inner_posts_tags.post_id
      INNER JOIN tags AS inner_tags ON inner_tags.id = inner_posts_tags.tag_id
    END
    add_to_conditions(options, tags.map { 'inner_tags.name = ?' }.join(' OR '), *tags)
  end

  handle_find_option(:query) do |options, query|
    if query.empty?
      add_to_conditions(options, 'false')
    else
      term = "%#{query}%"
      add_to_conditions(options, "posts.content LIKE ? OR posts.title LIKE ?", term, term)
    end
  end
end

Uma alternativa usando super:

class Post < ActiveRecord::Base
  class << self
    def find(*args)
      options = args.last.is_a?(Hash) ? args.last : {}
      add_tag_conditions(options)
      add_query_conditions(options)
      super
    end

    private
    def add_tag_conditions(options)
      if tag = options.delete(:tags)
        options[:select] ||= 'posts.*'
        options[:joins]  ||= ''
        options[:joins]  << <<-END
          INNER JOIN posts_tags AS inner_posts_tags ON posts.id = inner_posts_tags.post_id
          INNER JOIN tags AS inner_tags ON inner_tags.id = inner_posts_tags.tag_id
        END
        add_to_conditions(options, tags.map { 'inner_tags.name = ?' }.join(' OR '), *tags)
      end
    end

    def add_query_conditions(options)
      if query = options.delete(:query)
        if query.empty?
          add_to_conditions(options, 'false')
        else
          term = "%#{query}%"
          add_to_conditions(options, "posts.content LIKE ? OR posts.title LIKE ?", term, term)
        end
      end
    end

    def add_to_conditions(options, condition, *args)
      condition = args.empty? ? condition : [condition, *args]
      if options[:conditions].nil?
        options[:conditions] = condition
      else
        options[:conditions] = sanitize_sql(options[:conditions]) + " AND (#{sanitize_sql(condition)})"
      end
    end
  end
end