I gave an introductory presentation in VinSol. I am sharing it with you, this is not very explanatory as I focused on speech more. Please share your views.VinSol

| View | Upload your own

For example, lets assume that we need to add a column ‘role’ in users table(User model). In this case generate a migration like:

Output:

Here AddRoleToUser plays the main role. ‘Add’ specifies the we want to add column(s) and ‘User’ separated by ‘To’ specifies the table.

Similarly, if we need to remove a column ‘role’ :

Output:

Here RemoveRoleFromUser plays the main role. ‘Remove’ specifies the we want to remove column(s) and ‘User’ separated by ‘From’ specifies the table.

Isn’t it cool?

And then I started writing my own ruby script for same purpose but with some addition and modification. Commit notification script is that script, you can download and configure it with your SVN post commit hook as follows.

Add following line at the bottom of your post-commit file:

<br /> /usr/bin/ruby /var/www/repositories/project/hooks/commit-email.rb “$1″ “$2″<br />

* Please remember to change the path of you commit-email ruby script.

Now open commit-email ruby file and modify the following section according to your requirement:

<br /> # You can edit below</p> <p># Subject prefix<br /> sub = “[test_project@vinsol]” # A project ‘test_project’ is maitained at vinsol</p> <p>#list of users who will recieve commit notification<br /> recipients = ["bansalakhil30.10@gmail.com", "akhil@vinsol.com"]</p> <p># email which will appear in from email field<br /> from_user = “svn-notify@somedomain.com”</p> <p># your smtp settings here<br /> ActionMailer::Base.smtp_settings = { :address => ‘localhost’, :port => 25, :domain => ‘domain.com’}</p> <p># Do not edit below this line<br />

You are done with that, now onwards whenever someone commits the code, you’ll get the commit notification mail like:

Related posts:

1. Jquery Full Calendar with Ruby on Rails Contrary to popular belief, working on a client project gives...
2. SSL checklist for Ruby on Rails Applications Cross posted from darthsid The purpose of SSL is to...

Related posts brought to you by Yet Another Related Posts Plugin.

Now try following at console:

This will let you create three records in users table with same name, validates_uniqueness_of written in User class has no effect on it. validates_uniqueness_of automatically scoped with class names, that means it will not let you create two managers with same name or two customers with same name or two users with same name.

If you want uniqueness of an attribute in overall table, put the following code in some file in your lib dir and require that file in environment:

And then use validates_overall_uniqueness_of instead of validates_uniqueness_of.

Lets run rails application on https with pound. For that your machine should have:

* Pound installed with ssl support
* Pound and mongrels running

Now, First of all we need a ssl certificate, that can be generate by issuing “openssl req -x509 -newkey rsa:1024 -keyout mydomain.pem -out mydomain.pem -days 365 -nodes” . Give all the information it asks. Now copy mydomain.pem to /etc/pound/ directory(I am assuming that your pound.cfg file resides in /etc/pound/). Now put the following code in pound configuration file(/etc/pound/pound.cfg):

I am assuming that your mongrels are running at ports 8000, 8001, 8002, apache running at 8080 and pound is listening ports 443 & 80.
Restart pound, and you are done. With this configuration all requests for dynamic content at port 443(https) will get redirected to mongrels and requests for static content will get redirected to apache.

You may want to check if the request is https or not before serving the content. That can be done by adding a before_filter (defined below) in application.rb :

By adding this method as before_filter in application.rb your application will check for https, if the request is not of type https it will redirect to an https request.

You can also deploy your rails application with pound(a reverse proxy, load balancer and HTTPS front-end for Web server).

First you need to setup mongrel_clusters for your rails application by issuing ” mongrel_rails cluster::configure -e production -p 8000 -a 127.0.0.1 -N 3 -c ./ ” inside the rails application root directory(on client machine). This will create mongrel_cluster.yml in config directory. You can change parameters in this command, as -p 8000 specifies that mongrel instances will start up on port number starting 8000, -a 127.0.0.1 specifies that mongrel instances will listen to the localhost, -N specifies the number of mongrel instances and -c specifies the rails root directory.

Now you need to install pound(if not installed) by issuing following commands(as root):

• cd /opt/src
• wget http://www.apsis.ch/pound/Pound-2.3.2.tgz
• tar xzpf Pound-2.1.6.tgz
• cd Pound-2.1.6
• ./configure
• make
• make install

This will install pound in /usr/local/sbin/pound. In order to proceed further we need to create pound.cfg(pound configuration file) in /etc/pound/pound.cfg . Below is the content of pound.cfg:

</p> <p>User “pound”<br /> Group “pound”</p> <p>ListenHTTP<br /> Address 0.0.0.0<br /> Port 80<br /> Service<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8000<br /> End<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8001<br /> End<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8002<br /> End<br /> End<br /> End<br />

Start mongrel cluster by issuing mongrel_rails cluster::start in you app root directory, start pound by /usr/local/sbin/pound -f /etc/pound/pound.cfg , now you are done. Pound is listening the port 80 and redirect all requests to mongrel instances running on 8000, 8001, 8002.

* Please Note that we have configured pound at port 80, if port 80 is being used by apache or any other application pound will not start. You need to stop any service using port 80, if it is apache then stop apache, change line ‘Listen 80′ to “Listen 8080″ and start apache.

In a specific case, when apache is running at some port (let say 8080), you may want to use apache to serve static content of your application, in order to reduce some load from mongrels. In that case use the following:

</p> <p>User “pound”<br /> Group “pound”</p> <p>ListenHTTP<br /> Address 0.0.0.0<br /> Port 80<br /> Service<br /> URL “/(images|stylesheets|flash|javascripts)/”<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8080<br /> End<br /> Session<br /> Type BASIC<br /> TTL 300<br /> End<br /> End<br /> Service<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8000<br /> End<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8001<br /> End<br /> BackEnd<br /> Address 127.0.0.1<br /> Port 8002<br /> End<br /> End<br /> End<br />

This will redirect all requests for image, stylesheets, javascripts, flash to apache. Now we need to configure apache to serve those static content. Just add a virtualhost for that:

<br /> <VirtualHost *:8080><br /> ServerName example.com<br /> ServerAlias www.example.com<br /> DocumentRoot /var/www/html/example.com/public<br /> <Directory "/var/www/html/example.com/public" ><br /> Options FollowSymLinks<br /> AllowOverride None<br /> Order allow,deny<br /> Allow from all<br /> </Directory></p> <p> RewriteEngine On</p> <p> # For static files it’s good to avoid hitting your mongrel process<br /> # so let apache knows it should serve it directly<br /> # for a rails application it means, files in images / stylesheets / javascripts<br /> RewriteRule “^/(images|stylesheets|flash|javascripts)/?(.*)” “$0″ [L]</p> <p></VirtualHost><br />

Its all done. All requests for dynamic content at port 80 will be redirect to mongrel running at 8000, 8001, 8001 and requests for static content will be served by apache running at port 8080.

Related posts:

1. 11 Things to Consider Before Deploying Your Ruby on Rails Application At VinSol, we have been developing and deploying Rails applications...

Related posts brought to you by Yet Another Related Posts Plugin.

to start the solr server, it threw a heart breaking “Bad file descriptor” error, although acts_as_solr was working fine on one of my colleague’s linux machine.

I started digging around this and found that there is an issue in rake task that starts the solr server. Actually the problem was this rake task uses ‘fork’ which is not available on windows, also it only handles ‘ECONNREFUSED’ exception which is actually “Connection Refused” error raised by ruby on linux. But in windown it throws ‘EBADF’ which is “Bad file descriptor” error raised by ruby on windows.

So below is the hack for that:

Just add this to vendor/plugins/acts_as_solr/lib/taks/solr.rake, and start solr server on windows by issuing

1. rake db:test:purge
2. rake db:migrate
3. rake test

This default was not working with my last project As I was using RSpec for my project. I found that we can overwrite default way of building by creating a rake task named cruise in our project. Means by building CruiseControl will run your custom rake task only, so you have to take care of all other things i.e. migrate etc.

Hence I created following rake task in RAILS_ROOT/lib/tasks/custom_cc.rake

and it worked for my rails project using RSpec.

Related posts:

1. Jquery Full Calendar with Ruby on Rails Contrary to popular belief, working on a client project gives...

Related posts brought to you by Yet Another Related Posts Plugin.

This can be done by using svn hooks. Yes, svn has inbuilt hook functionality like pre-commit, post-commit, post-lock, post-unlock, pre-lock, pre-unlock, start-commit. We’ll use post-commit hook to get notifications.

First of all get a perl script from here http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/commit-email.pl.in and copy it to hooks directory inside your repository directory, lets say /var/www/repos/repository_name/hooks.
Make sure to rename it as commit-email.pl, ofcourse you need perl installed on your server. Now cd to hooks directory inside you repository directory. Rename post-commit.tmpl to post-commit, and chmod 755 to post-commit and commit-email.pl . Now open post-commit in you favorite editor, and put “/usr/bin/perl /var/www/repos/commit-email.pl –from svn-notify@example.com -s ‘SVN commit notification’ ‘$REPOS’ ‘$REV’ user_whom_to_notify@example.com, another_user_to_notify@example.com” at the bottom of that file. Now open commit-email.pl and make changes in configuration section according to your requirement and server, specially svnlook path.

Congrats!, You are done ;-) .

Now your server will send email notification to user_whom_to_notify@example.com, another_user_to_notify@example.com whenever someone commits.

**For security reasons, the Subversion repository executes hook scripts with an empty environment that is, no environment variables are set at all, not even $PATH or %PATH%. Because of this, a lot of administrators are baffled when their hook script runs fine by hand,but doesn’t work when run by Subversion. Be sure to explicitly set environment variables in your hook and/or use absolute paths to programs.

It worked for me, Please let me know if it works for you too.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.