If you’ve set all the APR/APU/APX paths and you are still having issues such as:

In file included from ext/boost/config/no_tr1/utility.hpp:21,

You may need to run:

yum install libstdc++-devel

Read my earlier post if you want Phusion Passenger to compile nginx with SSL support. If your nginx server already supports SSL, read on.

Phusion Passenger fills up most of the configuration in nginx.conf for you with a nice set of defaults. You just have to do a little more work if you want to modify the nginx configuration file to enable SSL on your site.

The first thing to do is purchase a SSL certificate and install it on your server. If you don’t know how, here’s a great post on installing SSL on Ubuntu with nginx. Once you’ve installed the certificate, you should be good to go.

Let’s say that you’ve got a domain name called mydomain.com and the root for your Ruby on Rails application is located at /home/mydomain/current/public on your server. The following shows a sample of the configuration required to get SSL enabled for your application:

server  {
    	       listen 80;
               server_name mydomain.com;
               root /home/mydomain/current/public;
               passenger_enabled on;
               rails_env production;
        }

# HTTPS server
server  {
               listen 443;
               server_name mydomain.com;
               root /home/mydomain/current/public;
               passenger_enabled on;
               rails_env production;

               ssl on;
               ssl_certificate /etc/ssl/certs/mydomain.com.crt;
               ssl_certificate_key /etc/ssl/private/mydomain.com.key;

               ssl_session_timeout  5m;
        }

Phusion Passenger or mod_rails has taken away almost all the pain once associated with deploying Ruby on Rails applications. Phusion Passenger recently added support for the nginx web server.  My application required SSL support, but Phusion Passenger does not by default compile nginx with SSL support. I’m new to System Administration and even newer to Unix, having used Windows Servers all my life, so I decided to document my steps to make it easier for others with the same problem.

Step 1: Download and unzip the source code for OpenSSL

Make sure to visit OpenSSL to determine the name of the latest source code tarball to download. In my case it was openssl-1.0.0-beta3.tar.gz

cd /tmp
wget http://www.openssl.org/source/openssl-1.0.0-beta3.tar.gz
tar -xvzf openssl-1.0.0-beta3.tar.gz

Step 2: Download and unzip the source code for nginx

Make sure to visit nginx to determine the name of the latest source code tarball to download. In my case it was nginx-0.8.14.tar.gz

wget http://sysoev.ru/nginx/nginx-0.8.14.tar.gz
tar zxf nginx-0.8.14.tar.gz

Step 3:Install and run Phusion Passenger

gem install passenger
passenger-install-nginx-module

• Watch Phusion Passenger do its thing and when it asks you “Automatically download and install Nginx?”, answer 2
• Specify the directory where you unzipped the nginx source code (/tmp/nginx-0.8.14 in my case)
• Specify the directory where you want to install nginx to (/opt/nginx in my case)
• When asked “Extra arguments to pass to configure script:”, reply with:

--with-http_ssl_module --with-openssl=/tmp/openssl-1.0.0-beta3

Keep in mind that if you downloaded the latest version of the source code, your values might be slightly different from mine.

That’s it! I’ve also posted a sample configuration file for nginx to enable SSL.

So I was revisiting how I deploy my rails site (brockbouchard.net) and I stumbled upon something called “Phusion Passenger”, also known as “mod_rails”.  I had been previously using Mongrel, but it turns out mod_rails makes deploying a Rails site as simple as placing the app in a directory on the web server.  No more ports or proxies or confusing Apache vhost files.  Check it out!

http://www.modrails.com/

Depois de muitos problemas para levantar um servidor em meu pc para poder rodar algumas aplicações que eu havia desenvolvido em rails e joomla, encontrei uma solução perfeita e também aprendi bastante sofrendo.

Descrição do sistema:Xubuntu, Apache 2

Solução:

Fechei a porta 80 e abri uma porta nova, de alto valor (acima de 1024), para cada aplicação que eu tinha:

#Listen 80

Listen 8080

Listen 8081

Listen 8082

etc

Criei um virtuahost para cada um, com sua respectiva porta *:8080, *:8081, etc

Pelos outros pcs da rede, chamava assim

http://10.68.40.72:8080

http://10.68.40.72:8081

http://10.68.40.72:8082

etc

Onde 10.68.40.72 é o ip do pc-servidor na rede (não é o ip do servidor web oficial-principal-autorizado da rede).

Da maneira acima, qualquer pc da rede pode acessar as aplicações rodando no meu pc.

Recentemente foi lançada a versão 2.0.5 do Phusion Passenger, também conhecido como mod_rails. Esta versão é compatível com Ruby 1.8.7 e Rails 2.3, que nem foi lançado ainda, além de incluir algumas melhorias na estabilidade e correção de bugs. Não testei nenhuma versão do mod_rails desde a primeira, mas pela freqüência de lançamento de novas versões e pelo que tem evoluído a cada versão, parece que tem tudo para se tornar um padrão para deploy de aplicações Rails.

Mais detalhes no blog do Phusion Passenger.

Hace un tiempo que me enteré que existe mod_rails y que tengo ganas de implementarlo en mi vps (dónde está alojado el sitio de rubylit entre otros) El vps tiene 300 MB de RAM en total, y hasta ahora tenía nada más que 30MB libres ( cada instancia de mongrel me consumia unos 40MB aprox.)

Así que aquí vamos con la instalación de mod_rails.

Primero vamos a instalar Ruby Enterprise Edition cómo recomiendan los chicos de passenger (mod_rails), también podemos usar el ruby convencional.

Para esto nos bajamos el .tar.gz con los sources y lo descomprimimos:

wget -c http://rubyforge.org/frs/download.php/47937/ruby-enterprise-1.8.6-20081205.tar.gz
tar -xvvzf ruby-enterprise-1.8.6-20080810.tar.gz

Yo lo voy a instalar en /opt que es dónde se instalan los paquetes que no vienen con la distro entonces quedaría:

/opt/ruby-enterprise-1.8.6-20080810/

Instalamos las libs necesarias para compilar ruby EE:

apt-get install g++ zlib1g-dev libssl-dev build-essential

Al intentar instalarlo me tiró el siguiente error, pero leyendo algunos mails de la lista de Ruby EE recomendaban ejecutar el instalador de la siguiente manera:

cd /opt/ruby-enterprise-1.8.6-20080810/
./installer --no-tcmalloc

y funcionó…

Ahora tenemos que crear una serie de links simbólicos para que nos quede la versión de Ruby EE instalada correctamente:

ln -fs /opt/ruby-enterprise-1.8.6-20080810/ /opt/ruby-enterprise
ln -fs /opt/ruby-enterprise/bin/gem /usr/bin/gem
ln -fs /opt/ruby-enterprise/bin/irb /usr/bin/irb
ln -fs /opt/ruby-enterprise/bin/rake /usr/bin/rake
ln -fs /opt/ruby-enterprise/bin/rails /usr/bin/rails
ln -fs /opt/ruby-enterprise/bin/ruby /usr/bin/ruby
ln -fs /opt/ruby-enterprise/lib/ruby/ /usr/lib/ruby

Ahora instalamos la gema de mysql

apt-get install libmysqlclient15-dev

/opt/ruby-enterprise-1.8.6-20080810/bin/ruby /opt/ruby-enterprise-1.8.6-20080810/bin/gem install mysql

Ya tenemos instalado Ruby EE entonces ahora vamos a instalar mod_rails.

bajamos los sources de passenger:

wget -c http://rubyforge.org/frs/download.php/47928/passenger-2.0.5.tar.gz
tar -xvvzf passenger-2.0.5.tar.gz

Instalamos las lib necesarias para compilar:

apt-get install ruby-dev libopenssl-ruby rubygems  apache2-prefork-dev build-essential

Instalamos apache prefork:

apt-get install apache2-mpm-prefork

Ahora tenemos que instalar mod_rails:

cd /opt/passenger-2.0.5
./bin/passenger-install-apache2-module

luego editamos el archivo /etc/apache2/mods-available/passenger.conf
y ponemos lo soguiente:

PassengerRoot /opt/passenger-2.0.5
PassengerRuby /opt/ruby-enterprise-1.8.6-20080810/bin/ruby

editamos el archivo /etc/apache2/mods-available/passenger.load
y ponemos lo siguiente:

LoadModule passenger_module /opt/passenger-2.0.5/ext/apache2/mod_passenger.so

luego tenemos que activar el modulo entonces ejecutamos el siguiente comando:

a2enmod passenger

Listo ahora lo único que tenemos que hacer cada vez que agregamos una app
es agregar un virtual host en apache.
Editamos el archivo /etc/apache2/sites-available/nueva_app.com
y ponemos lo siguiente:

    <VirtualHost *:80>
    ServerName www.nueva_app.com
    ServerAlias nueva_app.com
    DocumentRoot /var/www/apps/nueva_app.com/public
    RailsBaseURI /
    CustomLog /var/log/apache2/nueva_app.com.log "%h %l %u %t \"%r\" %>s %b"
   </VirtualHost>

Como pueden ver puse el archivo de log separado del lo general de apache.
luego de esto habilitamos el nuevo virtual host

a2ensite nueva_app.com

y reiniciamos apache:

/etc/init.d/apache2 reload

y listo.

Ahora en mi vps tengo 165MB de RAM libres, así que la migración fue productiva, cabe destacar que tuve que migrar de nginx a apache entonces todos los virtual hosts (státicos y dinámicos) que tenía creados en nginx los tuve que migrar a apache, pero no fue algo complicado.

Voici un premier post focalisé sur mes tests liés à l’hébergement d’applications Rails.

Depuis quelques temps, je fais tourner mes applis de cette manière :

• un cluster de process Mongrel (5-10 en général)
• un virtual host Nginx qui fait proxy et load-balancer

Au printemps 2008, la communauté Rails a déclaré (RubyInside et LoudThinking) que l’absence d’un vrai mod_ruby (ou rails) pénalisait fortement l’adoption de l’outil. Je l’ai constaté par moi-même a chaque présentation, les remarques fusent sur la complexité de l’hébergement.

Alors quelques farfelus se sont lancés dans le développement d’un module pour Apache qui permettrait de déléguer à Apache la gestion des process (leur lancement/extinction selon les besoins, le nombre max de process par appli ruby, …) et de se contenter d’un VirtualHost qui pointe vers le dossier principal d’une appli ruby.
Ce module a rapidement été surnommé “mod_rails” car il a assez vite permi de faire tourner des applis Rails, mais pas Merb, et autres framework à base de Ruby.
Son vrai nom est Passenger Phusion.
Depuis peu, il a atteint l’état “stable”, il permet de faire tourner d’autres framework, … et il gagne du coup une sacré popularité, à tel point que moi qui suis plutôt conservateur quand les choses marchent vraiment bien, je me suis laissé aller à faire un premier test de config, mais surtout à un comparatif de performance pour charger la page d’accueil d’une même appli Rails dans les 2 modes d’hébergement.

Situation commune

La machine est quasiment au repos ; MySQL tourne mais aucune autre appli Rails que celle de test n’est en service, pas de process lourd (copie, backup, transfert, …) au moment des tests.

Premier test : Nginx + Mongrel_cluster

J’ai mis en place un cluster de 30 process Mongrel et un VirtualHost dans Nginx pour le proxy/load-balancer. C’est ma config de prod courante (sauf que j’ai moins de process en général).

Un stress test avec ApacheBench : $ ab -n 1000 -c 50 http://serveur.dev/accueil

Au résultat il a fallu 94 secondes pour répondre aux 1000 requêtes, avec une moyenne de 10,58 req/sec

Aucun autre process gourmand et inutile ne tournait sur la machine (Apache était arrêté).

Second test : Apache + Passenger

J’ai configuré un Virtualost dans Apache2 avec un nombre maxi de process à 30

Un stress test avec ApacheBench : $ ab -n 1000 -c 50 http://serveur.dev/:81/accueil

Au résultat il a fallu 88 secondes pour répondre aux 1000 requêtes, avec une moyenne de 11,25 req/sec

Nginx était stoppé.

Conclusion

De la simplicité de mes tests et de leur rigueur très relative, je tire tout de même une première conclusion : ça va pas moins vite !

Ce qui veut dire que c’est a priori une solution aui est envisageable, moyenant des tests plus poussés.

Le grand bénéfice de tout ça serait certainement d’alléger mon environnement de dev. Ne plus avoir à paramétrer un cluster, un VHost, Monit, … pour une nouvelle instance de travail, ça sera un vrai progrès par le gain de temps.

Ensuite, pourquoi pas le mettre en environnement de production. La quantité de RAM dispo est assez importante, il suffit alors de permettre un grand nombre de process dynamiques pour que Apache s’adapte à la demande de manière plus souple.

Ça ne me fera pas changer d’avis quand à la qualité de Nginx en tant que serveur web ultra léger, particulièrement adapté pour les fichiers statiqueset très facile à configurer.

Unfortunately, the New Relic performance monitor for Ruby on Rails doesn’t work with mod_rails (Passenger). According to a support email from them it currently “only supports mongrel and thin (without sockets)”. They plan to support Passenger in the future. That’s great news because they provide an excellent performance monitoring tool which is very easy to install and use.

Update: New Relic has added support for mod_rails. I received this email from their excellent customer support:

I was just digging through my support emails and found a few people who had inquired about RPM supporting Phusion Passenger, aka mod_rails.

 

I wanted to let you know that we released a version of the agent with ‘beta’ support for Passenger.

 

If you’re interested, check it out and let us know how it works for you!

 

To try it out, just do:

 

script/install –force http://svn.newrelic.com/rpm/agent/newrelic_rpm

 

Bill Kayser

New Relic RPM Developer

Over Memorial Day weekend I migrated my Rails Application to Dreamhost using mod_rails (Passenger). It was not an entirely smooth process but I was also upgrading from Rails 1.8.x at the same time. That was compounded by making the foolish mistake of trying to rebuild my database using Rake migrations. (That’s a bad idea. I could have saved many hours by just uploading the schema)

Here is the procedure I followed (hat tip to Nock):

1. cd ~/
2. rails your_app_name -d mysql
3. Copy app/, database.yml, routes.rb, db/
4. Change public/.htaccess from .cgi to .fcgi
5. put your app into production mode (uncomment line 5 in environment.rb)
6. run rake db:migrate RAILS_ENV=production
7. chmod -R 755 ~/your_app_name/app
8. rm your_app_name/public/index.html
9. killall -USR1 dispatch.fcgi
10. killall -USR1 ruby

One comment on step 4. For some reason none of my stylesheets would load. Much of the advice gleaned from endless Google searches seemed to suggest that the problem would be fixed by setting the RewriteBase in /public/.htaccess. That turned out to not be the case.

My stylesheet problem was caused by having this line twice in my .htaccess file

RewriteRule ^(.*)$ dispatch.fcgi[QSA,L]

DO NOT uncomment the one before RewriteEngine On , as all the tutorials seem to imply, just change the .cgi to .fcgi in the block below it.

Thanks to Dreamhost for their stellar support over a frustrating (for me!) Memorial Day weekend. In the end, (as is so often the case), very little of the frustration was caused by Dreamhost or mod_rails but, rather, by some of the vagaries of Rails. I’m guessing that future deployments would be much smoother as this was my first time deploying to a shared hosting environment.

I use Dreamhost to host my websites and they have now added support for Passenger (a.k.a mod_rails). Ruby on Rails deployment hassles should be a distant memory soon!

If you’re looking for a cheap and cheerful hosting company for your Rails app, I highly recommend Dreamhost. It’s great for the solo developer (or small team) because for a small amount per year you can launch your site on a shared hosting service and then later easily migrate it to a virtual private server as your needs change. 

Recentemente foi lançado o Phusion Passenger, mais conhecido como mod_rails. Trata-se de um módulo Apache para Rails que promete oferecer configuração e deploy de aplicações mais simplificado do que com o Mongrel, além de ser mais estável e utilizar menos memória.

Tentei instalar o mod_rails e encontrei várias dificuldades. Inicialmente tentei instalar no CentOS 4.4, mas não consegui. Encontrei alguns conflitos de versões de pacotes (pré-requisitos do mod_rails), e ainda não consegui concluir a instalação.

Em seguida, tentei instalar no Ubuntu 7.10. As dificuldades foram menores, mas ainda assim não foi tão simples quanto parece pelo guia do usuário. Segue o passo-a-passo da instalação:

1. Instalar os pré-requisitos:

   sudo apt-get install apache2-mpm-prefork apache2-prefork-dev libapr1-dev
   

2. Instalar o gem do mod_rails:

   sudo gem install passenger
   

3. Definir as seguintes variáveis de ambiente:

   export HTTPD=/path/to/httpd
   export APXS=/path/to/apxs (ou apxs2)
   

4. Executar o script de instalação do módulo Apache:

   sudo /usr/lib/ruby/gems/1.8/gems/passenger-1.0.1/bin/passenger-install-apache2-module
   

5. Habilitar o mod_rails no httpd.conf do Apache, adicionando as linhas a seguir:

   LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-1.0.1/ext/apache2/mod_passenger.so
   RailsSpawnServer /usr/lib/ruby/gems/1.8/gems/passenger-1.0.1/bin/passenger-spawn-server
   RailsRuby /usr/bin/ruby1.8
   RailsEnv PROD
   

   A última linha acima define o ambiente Rails que será utilizado. Se você omitir esta linha, será usado o ambiente padrão (production).

6. criar um virtual host no Apache:

   <VirtualHost *:80>
     ServerName localhost
     DocumentRoot /var/www/rails/public
   </VirtualHost>
   

Na configuração acima, DocumentRoot é o diretório public da sua aplicação Rails.

Ao concluir estas configurações e reiniciar o Apache, minha aplicação funcionou, porém os arquivos que estão no diretório public (arquivos javascript, css e imagens) não estavam acessíveis. Para resolver este problema:

• habilite o mod_rewrite
• adicione à configuração do virtual host:

  <Directory "/var/www/rails/public" >
      Options         FollowSymLinks
      AllowOverride   All
  </Directory>
  

• reinicie o Apache

Assim, finalmente consegui fazer a aplicação funcionar corretamente. Ainda não fiz nenhum benchmark comparando o mod_rails com o Mongrel, mas todos os que encontrei até agora são favoráveis ao mod_rails, como estes:

• Benchmarking mod_rails against mongrel
• Phusion Passenger (mod_rails) Test-Drive

有人建議我可以 po 一些技術類的文章，所以來吧。

最近幾天針對伺服器軟體做了一些最佳化 (謎: 你不是期中考嗎？)，不知道眾鄉民有沒有覺得最近一、兩天網站的速度變快了？我是覺得有變快。包括也改了一些程式，因此寫一點筆記。有興趣寫 Ruby on Rails 程式的可以參考參考。

ksk 的利器？ mod_rails

網站運作速度變快，主要我覺得是因為我改用「號稱」極速的 mod_rails (Phusion Passenger) 這個專門為 Ruby on Rails 量身打造的 Apache 2 Module ，取代了原本一次開十隻 cluster 的 mongrel_rails 。

差別在於，之前是把十隻 cluster 一次全部開起來放在記憶體裡面當 daemons ，然後透過 mod_proxy 設定 proxy balancer 使 apache 可以調配 client 用戶該使用哪一個 daemon 來應對(詳細方法可以參考我去年寫的這篇文章)。而現在有了 mod_rails，直接讓 Phusion Passenger 去控制要有多少個 processes 開在記憶體中，甚至是有連線進來才啟動 rails，沒連線就統統關掉，有點像是 mod_php5 。

實作方法很簡單，照著這篇文章做就 ok 了，或是看官方的二行文教學也行 (真的只有 2 行指令就裝完了，當然改設定那些另當別論)。裝完之後把 apache2 重新啟動，記得先關掉原有的 mongrel_rails cluster 就是了。其實還真的有一種「Ruby on Rails 終於脫離 CGI 的影子了」的感覺，「檔案放上去就可以動了，不用開 ./script/server」。

所以我現在要暫時關站做 rake db:migrate 之類的事，還得先要把 #{RAILS_ROOT}/public 這個資料夾更名，假裝是關站 囧

進化到 rails 2.0.2、改用 will_paginate

一時興起把 config/environment.rb 裡面的 rails 版本換成 2.0.2 了，不知道 rails 2 是不是真的有讓 ruby on rails 變快？

可是因為這個換版本的動作，原本針對高中榜單做的分頁 (pagination) 竟然爛掉了。當初是抄這篇文章的方式去做的，那時候還在 rails 1.x 。結果換到 rails 2.0，似乎是 Paginate 這個 Class 不見了 (還是我找錯 namespace?)。

正在不知道該從何改起的時候，讓我找到了 will_paginate 這個東西，也不需要像之前那以自己寫(貼?) Class Methods 了，就直接引用他內建的東西即可。

先看 Installation 這篇文章，把 will_paginate 裝進系統，並載入你的 Ruby on Rails 專案，然後照這篇 Usage examples 做就行了。用的程式碼比之前少很多，也可以透過 css 去裝飾你 render 出來的分頁列長怎樣。

—

以上其實我不知道是不是真的有對 server 做到某種程度上的最佳化，因為同時我還把姓名查榜關掉了，光這個就可以省下很多資源。也許過幾天又把姓名查榜開起來，才會知道 mod_rails 到底有多大能耐吧。

—

ksk = 加速，日本 2ch 鄉民語。

Saatnya beralih ke Phusion Passenger (mod_rails/mod_rack). Passenger merupakan module apache httpd server yang dibuat awalnya agar dapat menjalankan aplikasi Rails di server apache (WebServer yg sudah well proven, dan paling banyak digunakan di seluruh dunia).

Apache memiliki banyak module yg dibuat oleh apache foundation community, atau pengembang 3rd party lain, sperti yg umum digunakan adalah mod_php, mod_python, mod_perl. Apache dapat menghandle request dengan membuat beberapa proses threard simultan yang diatur jumlahnya secara dinamis, dan jika terjadi error dapat melakukan reloading secara otomatis pula. Memanfaatkan kestabilan dari Apache Server, passenger lahir untuk memudahkan deployment aplikasi Rails, yg selama ini selalu menjadi momok menakutkan, dianggap menyulitkan,dan membutuhkan resource gede. Menjadi pain less deployment.

Kini passenger telah berevolusi menjadi mod_rack. Rack merupakan library ruby yg dibuat dengan tujuan menyeragamkan proses start webserver dengan menyediakan interface standard, sehingga apapun framework yg digunakan dan webservernya, tetap dapat berjalan, tanpa melakukan perubahan konfigurasi. Saat ini framework2 Ruby lain (Merb,Sinatra,Ramaze,Camping,dll) yg telah mendukung Rack dapat berjalan di apache dengan passenger tanpa masalah.

Passenger hanya dapat di install pada mesin *NIX. Windows mohon maaf, untuk saat ini ga masuk hitungan. Berikut langkah2 instalasi pada Linux Ubuntu (passenger Versi 2.0.2).

- Pertama2 pastinya harus telah menginstall Apache dan Ruby.
Dianjurkan menggunakan RubyEnterpriseEdition(REE), menurut janjinya Phusion, dpat mengurangi pemakaian memory hingga 30%.

- Download REE.deb, execute dan ikuti proses installasi hingga selesai
- Install Ruby Dev Header: sudo apt-get install ruby1.8-dev
- Install Apache Dev Header: sudo apt-get install apache2-prefork-dev
- Install APR Dev Header: sudo apt-get install libapr1-dev
- Install passenger, bisa compile dari source ataupun melalui rubygems
Jika ingin compile source, download sourcenya disini, ekstrak, dan masuk kedirektorinya.

- ./configure
- sudo make && make install

Jika rubygems
- sudo gem install passenger

- Jalankan: sudo passenger-install-apache2-module
ikuti hingga proses meminta untuk mengubah httpd.conf, tanpa berhenti dari proses installasi,

- edit file /etc/apache2/httpd.conf, tambahkan baris kode berikut
LoadModule passenger_module /opt/ruby-enterprise/lib/ruby/gems/1.8/gems/passenger-2.0.2/ext/apache2/mod_passenger.so
PassengerRoot /opt/ruby-enterprise/lib/ruby/gems/1.8/gems/passenger-2.0.2
PassengerRuby /opt/ruby-enterprise/bin/ruby

- Save dan exit proses edit httpd.conf

- Lanjutkan proses installasi dengan menekan enter

- Edit setting virtual host, sehingga aplikasi rails dpat berjalan
edit file /etc/apache2/sites-enabled/000-default, didalam tag <VirtualHost> dibaris paling akhir tambahkan kode berikut RailsBaseURI /rails_saya. Ini merupakan url yg nantikan akan diarahkan ke aplikasi rails anda.

- Save exit, dan proses installasi selesai.

- Create new Rails app : rails app_saya

- buat symlink dari folder public aplikasi rails tsb ke document root apache server(/var/www)
ln -s /home/irfani/Desktop/app_saya/public /var/www/rails_saya

- perhatikan rails_saya harus sama dengan url di RailsBaseURI

- restart apache server: sudo /etc/init.d/apache2 restart

- Buka browser masukkan url http://localhost/rails_saya. Ta daaa….Halaman welcome default rails akan tampil. Fast enaugh.

- Karena dalam env production, maka perubahan kode tidak akan seketika berdampak pada aplikasi rails yg telah dideploy, untuk itu diperlukan restart apache. Namun cara ini terlalu boros, dimana seluruh module apache2 lainnya akan di reload. Bagaimana jika hanya mereload aplikasi railsnya saja? caranya adalah : touch /home/irfani/Desktop/rails_saya/tmp/restart.txt

- Reload browser dan perubahan akan dijalankan

- passenger menjalankan rails dalam env Production, so ingat create database untuk production:
rake db:create:all dan lakukan migrate production rake db:migrate RAILS_ENV=production

Terimakasih. Salam dari Bali.rb untuk Komunitas Ruby Indonesia

If you’re running your low-volume Ruby on Rails app on mod_rails (Passenger) and have wondered why the first page takes 5 seconds or more to load, there is an excellent explanation here.

There’s a new gem called passenger which makes it very easy to deploy your rails application on a Apache2 server. Here is the website of the project: Passenger

There’s also a short screencast you can watch to see how easy rails deployment can be: Passenger Screencast (the video is made by Ryan Bates from railscasts so the voice should sound familiar )

I was once a respected coder. But for 5 years I’d designed ASIC’s using Verilog (where everything happens at once) and then for 5 years I’d turned to business. And it all changes in a decade. I’d let my skills lapse and in the interim C++ had morphed to Java and then suddenly CPU’s got really fast and scripting was back in vogue. 

I realized that my CS undergrad was quickly becoming worthless. Web programming was a complete mystery to me. (Whether that was really a problem is a philosophical question beyond the scope of a humble blog entry). Here is my road to recovery. In bullet point form amenable to PowerPoint and as buzzword compliant as possible.

Jan 1st, 2008: Resolve to brush up on programming skills.

Which language should I learn? Web development seems cool….what’s involved in that? Narrowed it down to a) the LAMP stack or b) Ruby on Rails. Do I want to be a) paid as a programmer or b) hip ?

I went with Hip. Rails it is.

Here are the steps (and mistakes) I took on the road to recovery:

1. Linux – I remember that: “ls -al” and all that. It’s the sine qua non for a real programmer.
2. F@(k. That’s a lot of variants of Linux. Go with Ubuntu because I’m semi-African.
3. Hmm… Windows XP is standard issue at work.
4. Get an old PC from my IT guy. Spend an entire day installing Ubuntu. Realize I’m now a web programmer so start again and install the server version. What the hell? What’s involved with web programming anyway. Will I be writing the client or the server?
5. Call college roommate who is on “tiger team” at Yahoo. He says: “Buy Pickaxe“. Sold. In a flash of environmental sympathy I buy the PDF version. It also saves $10. Print it out on corporate printer. Double sided to save the environment.
6. Need the Rails part: Buy “Agile Web Development with Rails“. We invested in an Agile software company so “agility” must be good.
7. Start reading. In the interest of time and an anxiety to see the global greeting I dispense with Linux and deploy InstantRails on Windows –> Instant gratification. (Nice to see those programmer types have dropped their antipathy towards Microsoft. I’m a web programmer. Even if it’s only on localhost. (Wow: It’s only February and I could compete with Amazon if I wanted to and if I knew where to buy all the books for my bookstore)
8. I have a bookstore up and running. No one can see it. That’s ok….how hard can deployment be.
9. March. Deploytment is hard. People don’t recommend Windows. Could I be the only person writing Ruby code in a Rails environment on Windows XP. Seems to be from my google searches.
10. Let’s reinstall Ubuntu Linux.
11. Install ruby gems. Rinse. Repeat. Rinse. Repeat. Check dependencies. Rinse Repeat. Rinse. Repeat.
12. Install MySQL. (It’s nice that I don’t need to think too much about the database. Seems like something business people should concern themselves with).
13. Stuff is working. Slow as all hell on this ancient PC but what the hell. People will wait for the page to load.
14. Becoming a problem that I can only work on my hobby at work. Can’t afford another PC at home.
15. VMware to the rescue. Downloading an Ubuntu VM on my home PC is a cinch. And hip. Which is important.
16. Realize I need a real hosting service. (Weeks of agonizing research). Settle on Dreamhost. (I love those guys!)
17. Deploy app. Hmmm…this is a f@(k1ng nightmare!
18. Passenger (mod_rails) is released a few days later. I realize I’m back on the cutting edge. Deployment is now piss easy.
19. www.assetcorrelation.com (Live as of June 1st, 2008 — 5 months start to finish)
20. Start to harass Google to show me some organic search love.

It’s been a wild ride. And not as hard as I thought. In the end, we return to the beginning. I still hate writing test benches. Hacking is still fun. And not having deadlines is the way to go.