| # A few examples about how to use Ruby for parsing files as we could do | |
| # with Awk or Grep. This is based on what I learn fro this post: | |
| # http://code.joejag.com/2009/using-ruby-as-an-awk-replacement/ | |
| # Split each line with ':' and print the first $F[0] field | |
| awk -F: '{ print $1 }' /etc/passwd | |
| ruby -F: -nae 'puts $F[0]' /etc/passwd | |
| # Parse the 'ps aux' output | |
| # It'll print the ID process for the 'jojeda' user |
By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:
/people/6
But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.
Please behave in a polite, considerate and inclusive manner in the channel at all times. People volunteer their time in the channel to help people like you with your Rails problems and some respect (in both directions) will go an extremely long way.
These rules are in place so that you can get the quickest and best support from #rubyonrails.
Rule #0: Show rather than tell. Explaining your problem with code, stacktraces or errors is always preferred to explaining it with just text. Show us what's happening, rather than telling us.
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
