1: Create a new Rails app - we'll call is 'deploytest'
$ rails deploytest
$ cd deploytest
2: Create a local Git repository for it
$ git init
$ git add *
$ git commit -a -m 'initial commit'
$ git status
3: Create a couple of Capistrano files
$ capify .
4: Edit config/deploy.rb
# The name of your app
set :application, "deploytest"
# The directory on the EC2 node that will be deployed to
set :deploy_to, "/var/www/apps/#{application}"
# The type of Source Code Management system you are using
set :scm, :git
# The location of the LOCAL repository relative to the current app
set :repository, "."
# The way in which files will be transferred from repository to remote host
# If you were using a hosted github repository this would be slightly different
set :deploy_via, :copy
# The address of the remote host on EC2 (the Public DNS address)
set :location, "ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com"
# setup some Capistrano roles
role :app, location
role :web, location
role :db, location, :primary => true
# Set up SSH so it can connect to the EC2 node - assumes your SSH key is in ~/.ssh/id_rsa
set :user, "root"
ssh_options[:keys] = [File.join(ENV["HOME"], ".ssh", "id_rsa")]
The only account on a default EC2 instance is root. You probably want to create a second user that is responsible for your application.
5: Copy your SSH public key to your EC2 node
$ scp -i ~/my-ec2-keypair ~/.ssh/id_rsa.pub root@ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com:/root/.ssh/authorized_keys2
NOTE the filename authorized_keys2 - not authorized_keys!!
6: Setup the EC2 node for Capistrano deployment.
From your LOCAL machine, not the EC2 node:
$ cap deploy:setup
7: Finally, deploy your application
$ cap deploy
You will see lots of output and with this dummy application some of those will report errors/warnings. Don't worry about that for now.
8: Check that the Deployment was successful
Connect to the EC2 node with SSH the regular way, cd to the app directory and check that everything is there. If that is all working then you are ready to deploy a real application and add custom tasks for managing the database, restarting the server etc.
Bear in mind that Capistrano add new 'releases' of your software in separate directories and symlinks the 'current' directory to the latest. So the root of your deployed application is the 'current' subdirectory.
Hope this will help you setting up your ec2 instance with capistrano.
SOAP4R is a Ruby library for accessing Web Services via SOAP. Recently I had a chance to explore SOAP4R. Here's how to get started with it.
Installation
Although Ruby 1.8.x comes with SOAP4R in its standard library, it is an old, buggy version. I highly recommend using the latest gem (1.5.8 as of the this update). It has one dependency, httpclient.
gem install soap4r --include-dependencies
Service
There are many services available to send SMS but I prefer to use,
MailServe-SMS
MailServe-SMS, text messaging service, is everything you need for fast, no-frills, no-fuss text messaging. A quick and easy way to send SMS.
Let’s explore these further.
Method 1: Read the WSDL at run-time
require "soap/wsdlDriver"
wsdl = "http://sms.qlc.co.in/smsapi.wsdl"
driver = SOAP::WSDLDriverFactory.new(wsdl).create_rpc_drive
A single call to a driver factory reads the WSDL file, and creates a driver class for you to use, complete with the methods defined by the service. What if your service requires authentication? The driver inherits methods from httpclient, so you can specify its options as you would for httpclient:
Once driver is get initialised you need to call SMS sending API i.e. SendSMSRequest.
driver.SendSMSRequest("username", "password", "sender_no", "from_no", "message")
Once This will return you response 200 SMS sent successfully on success else if the information submitted was wrong then 500 Information submitted was incomplete.
Method 2: Generate classes from WSDL
SOAP4R installs a command-line utility called 'wsdl2ruby' which can generate a client or server.
Coming soon…..
gem install rubyzip
Then, in the model that I’m using to generate the zip bundles, I add a couple “require” statements:
require 'zip/zip'
require 'zip/zipfilesystem'
class Album < ActiveRecord::Base
(...)
end
Next, I added a class method called bundle, which when called will use rubygem to generate the zip file. Note: the “permalink” attributes of Album and Artist are populated when an object of those models is created. I’m using them because it makes for nice filenames, too.
# create a zipped archive file of all the tracks in an album
def bundle(name = self.permalink, set = self.artist.permalink)
bundle_filename = "#{RAILS_ROOT}/public/uploads/#{set}-#{name}.zip"
# check to see if the file exists already, and if it does, delete it.
if File.file?(bundle_filename)
File.delete(bundle_filename)
end
# set the bundle_filename attribute of this object
self.bundle_filename = "/uploads/#{set}-#{name}.zip"
# open or create the zip file
Zip::ZipFile.open(bundle_filename, Zip::ZipFile::CREATE) {
|zipfile|
# collect the album's tracks
self.tracks.collect {
|track|
# add each track to the archive, names using the track's attributes
zipfile.add( "#{set}/#{track.num}-#{track.filename}", "#{RAILS_ROOT}/public#{track.public_filename}")
}
}
# set read permissions on the file
File.chmod(0644, bundle_filename)
# save the object
self.save
end
Next I added a method in my controller:
def create_bundle
album = Album.find(params[:id])
album.bundle
flash[:notice] = 'Album was successfully zipped.'
redirect_to album_url(album.artist, album)
end
And edit my routes.rb accordingly:
map.create_bundle 'create_bundle/:id', :controller => 'albums', :action => 'create_bundle'
Now it’s just a matter of creating a link in the view for the admin to click whenever he/she wants to generate the zip file:
<%= link_to('Create Album Zip', create_bundle_path(@album)) %>
…and a link for the user to click to download the zip file if it exists:
<% unless @album.bundle_filename.nil? %>
<%= link_to "Download Album Zip", @album.bundle_filename %>
<% end %>
That’s it! Refer to the rubyzip documentation for more info.
Ruby thumbnail generator is simple script which is ideal to use in your Ruby on Rails application to quickly generate thumbnails of any proportions. Just set width and height and get the image.
1. copy following code into /controllers/thumb_controller.rb
2. edit /config/routes.rb and add this line:
map.connect "thumb/*specs", :controller => "thumb", :action => "index"
3. create directory /imagelib/ in RoR's /public/ directory and
/image_cache/ inside /imagelib/ directoory
Now you can call /thumb/photo.jpg?w=400&h=350 and you will
see resized picture "photo.jpg". photo.jpg should be stored in
/public/imagelib/ directory. Off course you can change directory
structure if you wish just don't forget to edit thumb_controller.rb
than.
visit www.cleverleap.com/ruby-thumbnail-generator/
for more information
class ThumbController < ApplicationController
require 'gd2'
include GD2
def index
path = "imagelib/"
widthx = 500
heightx = 500
if params[:w] then widthx = params[:w].to_i
end
if params[:h] then heightx = params[:h].to_i
end
filepath = path + params[:specs].join("/")
format = filepath.split(".").last
filename = params[:specs].last.split(".").first
digest = Digest::MD5.hexdigest( filepath )
cachefile = digest + "-" + widthx.to_s + heightx.to_s + "." + format
picfile = filepath
cachedpicfile = path + "image_cache/" + cachefile
if File.exists?(cachedpicfile) && (File.stat( cachedpicfile ).mtime.to_i > File.stat( picfile ).mtime.to_i)
picsource = cachedpicfile
cache = true
elsif File.exists? picfile
picsource = picfile
end
if cache == true
@pic = File.new(picsource).read
else
i = Image.import(picsource)
if i.size[0] > i.size[1]
if i.size[0] < widthx then width = i.size[0]
else width = widthx
end
height = width * i.size[1] / i.size[0]
else
if i.size[1] < heightx then height = i.size[1]
else height = heightx
end
width = i.size[0] /(i.size[1] / height)
end
i.resize! width, height
if format == "gif" then @pic = i.gif
elsif format == "png" then @pic = i.png
else @pic = i.jpeg 80
end
i.export(path + 'image_cache/' + cachefile )
end
cgi = CGI.new
cgi.out("type"=>"image/jpeg") { @pic }
render :nothing => true
end
end
Progress on god is moving along as quick as ever. Most interestingly you'll find several useful new command line functions:
god status prints out the status of each Watch
god log shows realtime logs for a specific Watch (even if you don't have god logging to file)
god load loads or reloads a config file into a running god instance
god terminate stops all Watches and then stops god (useful when testing your setup)
The logging system has been beefed up with proper timestamps and criticality levels. Log messages are more complete overall. You can also get the STDOUT/STDERR of a god-daemonized process written to a log file by specify 'w.log = ' in your Watch config.
If you let god daemonize your process for you, there's no need to provide a stop command. A default killing lambda will take care of gracefully (or not so gracefully if necessary) stopping your god-daemonized process.
The validity of your config file is checked better than previous versions to point you to the problem area of your config.
The bug that prevented group control from working has been fixed so you can now start/stop/etc groups of Watches.
Updated documentation is now available on the website:
http://god.rubyforge.org/
WHAT IS GOD?
God is an easy to configure, easy to extend monitoring framework written in Ruby.
Keeping your server processes and tasks running should be a simple part of your deployment process. God aims to be the simplest, most powerful monitoring application available.
INSTALL
sudo gem install god
FEATURES
- Config file is written in Ruby
- Easily write your own custom conditions in Ruby
- Supports both poll and event based conditions
- Different poll conditions can have different intervals
- Easily control non-daemonized processes
EXAMPLE
The easiest way to understand how god will make your life better is by looking at a sample config file. The following configuration file is to keep the mongrels running:
# file: application_name.god
# run with: god -c /path/to/application_name.god
#
# This is the actual config file used to keep the mongrels of
# application.com running.
RAILS_ROOT = "/var/www/application_name/current"
%w{8001 8002 8003}.each do |port|
God.watch do |w|
w.name = "application_name-mongrel-#{port}"
w.interval = 30.seconds # default
w.start = "mongrel_rails cluster::start --only #{port} \
-C #{RAILS_ROOT}/config/mongrel_cluster.yml"
w.stop = "mongrel_rails cluster::stop --only #{port} \
-C #{RAILS_ROOT}/config/mongrel_cluster.yml"
w.grace = 10.seconds
w.pid_file = File.join(RAILS_ROOT, "log/mongrel.#{port}.pid")
w.behavior(:clean_pid_file)
w.start_if do |start|
start.condition(:process_running) do |c|
c.interval = 5.seconds
c.running = false
end
end
w.restart_if do |restart|
restart.condition(:memory_usage) do |c|
c.above = 150.megabytes
c.times = [3, 5] # 3 out of 5 intervals
end
restart.condition(:cpu_usage) do |c|
c.above = 50.percent
c.times = 5
end
end
end
end
|
Configuration for nginx and mysql
I found a gr8 post for sample configuration here
DOCS
Detailed documentation is available at http://god.rubyforge.org/
Original Source...
Ruby on Rails does a decent job in handling security concerns in the background. You will have to configure your application to avoid few security attacks while plugins would be required for many security concerns which are not at all or poorly managed by rails.
Authentication
Authentication is the foremost requirement of most of the web applications to authenticate and give privileges to their users. Apart from normal authentication mechanism rails have plugins for OpenID, CAS and Access Control. Build your own authentication system only if your requirements are very unique or you do not trust other implementations.
Plugin - Restful Authentication (recommended) - easy to use and you can tweak it according to your requirements.
http://railscasts.com/episodes/67
http://svn.techno-weenie.net/projects/plugins/restful_authentication/
Build your own authentication. You should rarely need to do this ... Restful Authentication is quite flexible.
http://www.aidanf.net/rails_user_authentication_tutorial
OpenID - a universal authentication system to avoid use of multiple username and password on the Internet. OpenID is getting quite famous now-a-days.
http://media.railscasts.com/videos/068_openid_authentication.mov
http://agilewebdevelopment.com/plugins/openidauthentication
Access Control : To easily proivde different priviliges to your users. There are a lot of cool plugins available for access control.
https://opensvn.csie.org/traccgi/tobionrails
http://code.google.com/p/rolerequirement/
http://agilewebdevelopment.com/plugins/activeacl_rails_authorization_system
Centralized Authentication Server - is used to implement single login/password for your users across multiple application. It can also be used for a single sign-on system. For example, Gmail and Google Reader have a single sign-on between them.
http://agilewebdevelopment.com/plugins/cas_authentication_filter
Use Google Authentication API to let your users login using their google username and password.
http://rubyforge.org/projects/asgoogleaccount/
More Plugins :
Rails inbuilt Authentication - http://ryandaigle.com/articles/2006/12/4/whats-new-in...
Acts_as_authenticated - http://technoweenie.stikipad.com/plugins/show/User+Authentication
Super Simple Authentication - http://ariejan.net/2007/08/24/super-simple-...
- Model -
SQL Injection
The problem arises when metacharacters are injected into your queries to database. Rails has a very good support to avoid SQL injection if you follow conventions in issuing queries to your database.
Description :
http://manuals.rubyonrails.com/read/chapter/43
Alternate Solution - use hash for specifying conditions in #find
http://weblog.rubyonrails.org/2006/11/26/1-2-new-in-activerecord
Activerecord Validation
To validate the contents of model object before records are created/modified in the database. Activerecord validations are very useful over database data-type constraints to ensure values entered into the database follow your rules. You might have javascript validations for forms but javascript can easily be switched off. Use javascript validations only for better user experience.
Description :
http://rails.rubyonrails.com/classes/ActiveRecord/Validations/ClassMethods.html
Conditional validation using
n and :if options. Checkout this cool video
http://media.railscasts.com/videos/041_conditional_validations.mov
Be careful using validates_uniqueness_of, it has problems when used with :scope option. Open bug tickets :
http://dev.rubyonrails.org/ticket/5608
http://dev.rubyonrails.org/ticket/9235
http://dev.rubyonrails.org/ticket/8811http://dev.rubyonrails.org/ticket/8774
Use :allow_blank to pass validations if value is nil or empty string
http://ryandaigle.com/articles/2007/9/5/what-s-new-in-edge-rails-validations-now-allow_blank
Testing Validations - do read the comments in this article
http://blog.jayfields.com/2006/12/rails-unit-testing-activerecord.html
Useful Tips
- Its easy to manage 'nil' values using
:allow_nil, its quite handy. For ex: set :allow_nil => true in validates_uniqueness_of to check uniqueness of non-nil values and ignore nil values
- validates_presence_of is not required if you are using validates_format_of, unless regular expression accepts empty string.
Creating records directly from parameters
While creating database records directly from form params, a malicious user can add extra fields into the params and manually submit the web page which will set values of fields which you do not want user to set.
Description :
http://manuals.rubyonrails.com/read/chapter/47
Alternate Solution - Trim the parameters to keep the required keys and remove the others.
http://wiki.rubyonrails.org/rails/pages/HowToPreventFormInjection
- Controller -
Exposing methods
Use private and protected in controller for methods which should not be actions. Actions are pubic methods and can be invoked from the browser.
hide_action : If non-action controller methods must be public, hide them using hide_action.
http://www.mathewabonyi.com/articles/2006/08/11/hide_action-a-hidden-treasure
Be careful of bypassing private and protected using meta-programming
http://dev.zeraweb.com/design-blog-14
Authorize parameters
Always authorize user request. By tweaking form parameters or url a user can send request to view/modify other users information if there is no proper authorization of parameters.
For example :
## To find information of an order which belongs to a particular user.
#Incorrect :
@order = Order.find(order_id)
#Correct :
@order = @user.orders.find(order_id)
|
Do not ignore hidden fields - a user can easily modify their value, so suspect them similar to params[:id]
http://searchsecurity.techtarget.com/tip/1,289483,sid14_gci1153816,00.html
Filter sensitive logs
Prevent logs of sensitive unencrypted data using #filter_parameter_logging in controller. The default behavior is to log request parameters in production as well as development environment, and you would not like logging of password, credit card number, etc.
Video Tutorial
http://railscasts.com/episodes/9
Cross Site Reference(or Request) Forgery (CSRF)
In a CSRF attack, the attacker makes victim click on a link of his choice which would contain a GET/POST request and causes web application to take malicious action. The link could be embedded in a iframe or an img tag. Its recommended to use secret token while communicating with user to avoid this attack.
Its little complex to understand this attack. So, only those readers who are very enthusiastic to know about it, please read the Description below. Rest can directly move ahead to use the plugin.
Description :
http://isc.sans.org/diary.html?storyid=1750
http://en.wikipedia.org/wiki/Cross-site_request_forgery
Use Get and Post appropiately (note : Both get and post are vulnerable to CSRF)
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1
Example - Gmail CSRF security flaw
http://ajaxian.com/archives/gmail-csrf-security-flaw
Plugin - CSRF Killer (recommended) - it requires edge rails
http://svn.techno-weenie.net/projects/plugins/csrf_killer/
http://activereload.net/2007/3/6/your-requests-are-safe-with-us
Secure action - http://code.google.com/p/secure-action-plugin/
Security extension - http://svn.aviditybytes.com/rails/plugins/security_extensions/
Minimize session attacks
If an attacker has session-id of your user, he can create HTTP requests to access user account. An attacker can get session-id by direct access to user machine or is able to successfully run malicious scripts at user machine. In this section we will talk about how to avoid or minimize the risk if attacker has user session-id. Following steps are helpful:
- Store IP Address, but creates problem if user moves from one network to another.
- Create a new session everytime someone logs in.
- Expire session on user logout, user is idle for a time period or on closing of browser/tab. For maximum security expire sessions on all the three conditions.
Code for session expiry on timeout
## Timeout after inactivity of one hour.
MAX_SESSION_PERIOD = 3600
before_filter :session_expiry
def session_expiry
reset_session if session[:expiry_time] and session[:expiry_time] < Time.now
session[:expiry_time] = MAX_SESSION_PERIOD.seconds.from_now
return true
end
|
Plugin - Session Expiration for session expiry on timeout
http://www.naffis.com/2007/5/22/automatically-expiring-sessions-in-rails
Do not put expiry time in the cookie unless your cookie information is properly encrypted. If not, use server side session expiry.
http://wiki.rubyonrails.org/rails/pages/HowtoChangeSessionOptions
Persistent session / login in rails - global setting in enviornment.rb
|
ActionController::Base.session_options[:session_expires] = <i>say after two years</i>
|
Persistent session / login in rails - to give your users a feature - remember me
http://blog.codahale.com/2006/04/08/dynamic-session-expiration-times-with-rails/
http://www.onrails.org/articles/2006/02/18/auto-login
http://livsey.org/2006/6/30/persistent-logins-in-rails
Stop spam on your website from DNS Blacklist
Avoid access to your website from IP addresses which are present in DNS Blacklist(DNSBL).
Plugin - DNSBL check
http://spacebabies.nl/dnsbl_check/
Caching authenticated pages
Page caching does bypass any security filters in your application. So avoid caching authenticated pages and use action or fragment caching instead.
- View -
Cross site scripting(XSS) attack
Cross Site Scripting is a technique found in web applications which allow code injection by malicious web users into the web pages viewed by other users. An attacker can steal login of your user by stealing his cookie. The most common method of attack is to place javascript code on a website that can receive the session cookie. To avoid the attack, escape HTML meta characters which will avoid execution of malicious Javascript code. Ruby on Rails has inbuilt methods like escape_html() (h()), url_encode(), sanatize(), etc to escape HTML meta characters.
Description
http://manuals.rubyonrails.com/read/chapter/44
Can we avoid tedious use of h() in views?
http://wiki.rubyonrails.org/rails/pages/HowToEscapeHTML
Sanitize() is used to escape script tags and other malicious content other than html tags. Avoid using it ... its unsecure. Use white_list instead.
http://www.rorsecurity.info/2007/08/17/dont-use-strip_tags-strip_links-and-sanitize/
White_list plugin
http://svn.techno-weenie.net/projects/plugins/white_list/README
Anti-spam form protection
Use Captcha or Javascript based form protection techniques to ensure only human can submit forms successfully.
When using Captcha do ensure the following :
- Images are rendered on webpage using
send_data and are not stored at the server, because its not required to store images and are redundant.
- Avoid using algorithm used by standard Catpcha plugins as they can easily be hacked, instead tweak an existing algorithm or write your own.
- Use a Captcha which does not store secret code or images in filesystem, as you will have trouble using Captcha with multiple servers.
Tutorial - a nice article on concepts of captcha
http://revolutiononrails.blogspot.com/2007/04/pedo-mellon-minno-or-captcha-on-rails.html
Plugin - ReCaptcha (recommended)
http://recaptcha.net/
http://ambethia.com/recaptcha/
Plugin - BrainBuster - a logic captcha based on simple puzzles, math and word problems. By default, it has limited set of problems and you would have to come up with large set of your own problems.
http://robsanheim.com/brain-buster
Plugin - Simple Captcha (not recommended) as it breaks all the must have features of a good Captcha implementation.
http://expressica.com/2007/03/23/simple_captcha_1_0/
For less critical systems like blogs, a more user-friendly option can be use of CSS based technique or JavaScript based plugin unlike Captcha. Both JavaScript and CSS based techniques can only avoid spam from dumb or general bots. If an hacker specifically targets your site or bot is smart enough, you are dead, so be careful.
CSS based Negative Captcha - http://damienkatz.net/2007/01/negative_captch.html
Inverse Captcha for Mephisto - http://www.artweb-design.de/projects/mephisto-plugin-inverse...
JavaScript based Form Spam Protection - http://form-spam-protection.googlecode.com/svn/form...
Captcha with Multiple Servers
http://upstream-berlin.com/blog/2007/08/17/captchas-with-rails-and-multiple-servers/
Hide mailto links
Mailto links in a webpage can be attacked by e-mail harvesting bots. Use the plugin CipherMail to generate a 1024 bit random key and obfuscate the mailto link.
Plugin - CipherMail
http://agilewebdevelopment.com/plugins/ciphermail
Use password strength evaluators
A lot of people have used password strength evaluators simply because its used by google in their registration form. You can use it to help your users register with strong password. But I don't think its a must have security addon. Uptill now I have not found a good algorithm to assess strength of a password, but some of them are reasonable.
Also, if there is an open source tool or algorithm for evaluating password strength, it can easily be broken. So, you might consider tweaking the algorithm or building one from scratch.
Tools
http://www.certainkey.com/demos/password/http://www.jeffro2pt0.com/ajax-powered-password-strength-meter/
http://www.geekwisdom.com/dyn/passwdmeter
http://www.jvoorhis.com/articles/2006/04/06/automatic-password-suggestion-for-your-rails-app
- Miscellaneous -
Transmission of Sensitive information
Use SSL to encrypt sensitive data between transfer from client to server. SSL hits server performace, so you might consider using SSL only for few pages which transfer sensitive data to and fro.
Plugin ssl_requirement
http://svn.rubyonrails.org/rails/plugins/ssl_requirement/README
Mongrel, rails, apache and SSL
http://blog.innerewut.de/2006/06/21/mongrel-and-rails-behind-apache-2-2-and-ssl
Controller in SSL subdomain
http://www.railsonwave.com/railsonwave/2007/7/10/howto-put-a-controller-under-a-ssl-subdomain
Sample SSL code in rails
http://blog.caboo.se/articles/2007/4/21/sample-rails-app-branch-with-ssl
File upload
Be very careful when you allow your users to upload files and make them available for other users to download.
Description
http://www.rorsecurity.info/2007/03/27/working-with-files-in-rails/
Must read - Section 26.7 of Agile web development with rails - 2nd edition
http://www.pragmaticprogrammer.com/titles/rails2/
In place file upload
http://kpumuk.info/ruby-on-rails/in-place-file-upload-with-ruby-on-rails/
3 plugins for file upload reviewed at :
http://www.flex888.com/2007/03/21/three-ruby-on-rails-file-upload-plugins-reviewed.html
Secure your setup / environment
http://www.igvita.com/blog/2006/10/10/securing-your-rails-environment/
Proper Mysql configuration
http://www.rorsecurity.info/2007/02/25/securing-mysql/
http://www.rorsecurity.info/2007/02/27/rails%e2%80%99-friends-securing-mysql-continued/
Use good passwords
http://en.wikipedia.org/wiki/Password_strengthhttp://www.rorsecurity.info/2007/06/05/use-good-passwords/
Security plugins directory
http://agilewebdevelopment.com/plugins/category/1
http://www.railslodge.com/plugins
http://railsify.com/categories/security-production
Original Source http://www.quarkruby.com/2007/9/20/ruby-on-rails-security-guide
This tutorial will cover how to read (or parse) an excel file with ruby. Here's how you can do the same thing.
Installing Parseexcel
Parseexcel is a ruby port of the perl parseexcel module.
It's installable via a nice gem like so:
gem install parseexcel
That's that, now remember since it's a gem library we have to tell our script to use the gem libs when we run the script from the console using the -rubygems switch.
Using Parseexcel
Parseexcel is a very straight forward library, you can't do too much with it, but it gets the job done.
Getting a Workbook
Spreadsheet::ParseExcel.parse(filenameandpath)
This returns the actual excel file's workbook, from there we need to determine what worksheet we're on.
Getting a Worksheet
worksheet = workbook.worksheet(0)
Will return the first worksheet, you could also use the each method on the workbook to iterate over all the worksheets.
Iterating over rows and columns
The worksheet object has a very nice each method that will allow us to iterate over the rows like so
worksheet.each { |row|
j=0 i=0
if row != nil
row.each { |cell|
if cell != nil
contents = cell.to_s('latin1')
puts "Row: #{j} Cell: #{i} #{contents}"
end
i = i+1
}
j = j +1
end
}
Getting Cell Data
- Getting a String: cell.to_s('latin1')
- Getting a Float: cell.to_s('latin1')
- Getting a Int: cell.to_i
- Getting a Date: cell.date
Getting A Specific Cell
cell = row.at(3) #returns cell at column 3
A basic script for dumping an excel file
require 'parseexcel'
#Open the excel file passed in from the commandline
workbook = Spreadsheet::ParseExcel.parse(ARGV[0])
#Get the first worksheet
worksheet = workbook.worksheet(0)
#cycle over every row
worksheet.each { |row|
j=0
i=0
if row != nil
#cycle over each cell in this row if it's not an empty row
row.each { |cell|
if cell != nil
#Get the contents of the cell as a string
contents = cell.to_s('latin1')
puts "Row: #{j} Cell: #{i}> #{contents}"
end
i = i+1
}
end
}
To run the script, remember to use the -rubygems switch so that you can find the parsexcel library.
ruby -rubygems excelparse.rb myfile.xls
The code displays all the subdirectories and files listed in the the main directory, and also displays these items as a link so that the following subdirectories can become the directories and diaplay the corresponding elements
IN CONTROLLER...............
DEF listing
if (params[:dir] !=nil) @path = params[:path]+"/"+params[:dir]
else @path ="D:/Folder_name" end
@dirEntries = Dir.entries(@path)
@dirEntries.reject! { |filename| filename.starts_with? '.'}
end
IN VIEWS.........<%= javascript_include_tag :defaults %>
<% for dir in @dirEntries %> <%= link_to "#{dir}", :action => 'listing', :path => @path, :dir => dir %><br/>
<% end %>