Rails Summer of Code, Week 5, July 22, 2010 from Cindy Royal on Vimeo.

Rails Summer of Code, Week 4, July 15, 2010 from Cindy Royal on Vimeo.

This week I cover error handling in ruby (begin-rescue-end) and rails (logger and object.errors) I then move to talk about (Asynchronous Javascript) Ajax in general including common caveats,  I then talk about Ajax with rails 3.

Right now the default heroku server doesn’t support rails3, so we will need to do some minor modifications, the direct documentation can be found here:  http://docs.heroku.com/rails3#serving-static-assets ,  http://docs.heroku.com/bamboo ,  and  http://docs.heroku.com/quickstart

For a play by play of how to do it follow these directions, and post to the list if you have any questions:

1) Get your application working

2) Add this line of code to : config/environments/production.rb

config.serve_static_assets = true

3) Then you need to install git On a Mac, Windows, or UNIX/Linux
4) In terminal (or command prompt) navigate to your application then execute:

git init
git add .
git commit -m "new app"

5) Sign up through heroku then install the heroku gem:

sudo gem install heroku
heroku keys:add
  Enter your Heroku credentials.
  Email: joe@example.com
  Password:
  Uploading ssh public key /Users/joe/.ssh/id_rsa.pub

6) Deploy your app (still in terminal)

heroku create --stack bamboo-ree-1.8.7 --remote trybamboo
git push trybamboo master

7) Confirm the application is still working by going to the url listed in the output of your terminal. Like:  http://glowing-wind-35.heroku.com/ you will also want to migrate the database:

heroku rake db:migrate --stack bamboo-ree-1.8.7 --remote trybamboo

8) Once you have any errors ironed out, then migrate your heroku install to the main server:

heroku stack:migrate bamboo-ree-1.8.7
git push heroku master
heroku rake db:migrate

9) If you got an error in (8) then you may need to force a rebuild if you didn’t make changes to your code:

heroku stack:migrate bamboo-ree-1.8.7
echo >> Rakefile && git commit -a -m "migrating to bamboo stack"
git push heroku master

10) Now when you make any changes to your application and want to re-deploy you can:

git add .
git commit -m "summary of my changes here"
git push heroku master

Give that a shot, and let me or the group know if you have any problems.  I expect to see an application online per-student by Wednesday evening. That means I expect lat minute questions on the mailing-list by Tuesday. (hint: try it right now, seriously quit watching cartoons, take 10 minutes and deploy an app…its fun! )

Good luck and happy heroku-ing.

Rails Summer of Code, Week 3, July 8, 2010 from Cindy Royal on Vimeo.

This week I cover functional testing, has_many, belongs_to, HABTM, has many :through, and the association database structure. I finish up the section with some impromptu hacking to demonstrate how you can move controller logic to the model, to create re-usable code chunks.

Rails Summer of Code, Week 2, July 1, 2010 from Cindy Royal on Vimeo.

Welcome to Rails Summer of Code.  I’m leading at University of Texas in Austin class through the excellent Agile Web Development with Rails (beta version for Rails 3). This second week I focused on ruby data structures, and the difference between class and instance methods. I then talked about migrations, scaffolding, generators, validation, and unit tests. Recommended Reading: Chapters 3, 4 & 5

Rails Summer of Code – Week 1, June 24, 2010 from Cindy Royal on Vimeo.

Rails Summer of Code – Week 1, June 24, 2010 from Cindy Royal on Vimeo.

This is a first run class, so if you have some constructive criticisms, let me know!

Get your your book, watch the video, and get your Rails on!

<gem env install path>/gems/authlogic-oauth-1.0.8/lib/authlogic_oauth/helper.rb

def oauth_button(name, options = {})
 "<input type='submit' value='#{options[:value]}' name='#{name}' id='user_submit' class='#{options[:class]}'/>".html_safe
end

Good luck and happy Oauth-ing!

–

Richard Schneeman

Disposable Email

Since we released the app, in one day we doubled the number of disposable email addresses we’ve created in the last 30 days. Though the service is essentially the same as WhySpam.Me the difference is the all in the UI. People seem to love the idea of generating sketchy email addresses for sketchy websites.

So this:

reload!

Acts as if you just did this:

exit
script/console

So not only does it require one less command, but you can still use all previously defined variables. Awesome!

mate .gitignore

add the file you don’t want to show up in the public repository, such as config/environment.rb

Then you can call this command to force the branch to be filtered. Note this command will remove the actual file from your hard drive, so make sure to have a backup.

git filter-branch --force --tree-filter  'rm config/environment.rb' HEAD

You can then push your newly super secure repository.

git push --force origin master