“Featuring the best daily NoSQL news, articles and links covering all major NoSQL projects and following closely all things related to NoSQL ecosystem. Everything you need and want to know about NoSQL.”

Based on:http://railsillustrated.com/getting-started-with-tokyo-on-osx.html

There is one tweak for the Ruby binding:ARCHFLAGS=”-arch x86_64″

I hope this helps someone, I know it has me.

• Warm up with humming high to low
• Lip roll scales
• Pitch exercises - this is where I play a note on the piano and match the pitch and hold for 10 sec
• Nay, nay, nay  scales
• Warm down the same as warming up

Also, here’s a nice cheetsheet: http://cheat.errtheblog.com/s/git

# Sets up a local branch
git branch my_test

# Creates the remote branch
git push origin my_test

# Deletes a remote branch
git push origin :my_test

# Delete branch locally
git branch -d my_test

UPDATE: (5/27/2009)
Get a remote branch that exists on the server but not locally (tracking is set by default)

git checkout -b my_test_prod origin/my_test_prod

ALSO

Edit Global Bash ProfileYou need to edit the global bash profile as follows:

1. Open the Terminal application.
2. Type sudo pico /etc/profile
3. You will be prompted to enter your password.
4. Add the following text to the end of the file:

   export PATH=/Library/PostgreSQL8/bin:$PATHexport PGDATA=/Library/PostgreSQL8/dataPostgreSQL8 in the above text might be something different depending on the version you installed. Check on your computer in the HardDrive/Library/ folder to verify the name of your installed PostgreSQL folder.

5. Press Ctrl+x to Exit. Press y to save the changes. Press the Return key to save the file.

Copied from: http://www.studiotips.net/docs/tips_sql/postgresql/installingpostgresqlonmac.html

Enter acts as role.  Written with my friend Jon Morton, AAR allows for role/permission simplicity through-out a Rails application.   We followed these guidelines when writing AAR - Had to:

• have model based security
• protect Controller actions
• simple to code in the View
• hide items easily in the View
• database driven, have no ACL list in the code
• allow multiple roles
• and handle permission conflict intelligently

Understanding Users/Roles/Permissions
AAR’s basic principle is that you should not give special permissions directly to the User.  All permissions are given to a Role.  If there is a snowflake** who needs X permission then I copy an existing Role and add the permission.  This way if (or when) that user is gone the permissions and are preserved.

Installation can be a simple as downloading the app, putting it in your vender/plugins directory and adding “include ActsAsRole” at the top of your controllers/application.rb.    Correction.  There are models and relationships that need to be set up that I have not explained.  I’ll work on updating the README to include this. And add some rake tasks to the plugin to create the models.  See the DB Schema PDF to see the model associations.

EXAMPLE of using AAR:

if has_access?(users_path)do something…end

OR

if has_access?(:controller => ‘users’, :action => ‘index’)do something…end

In Part 2, I’ll have a screencast and a test app.

Links:
git AAR
model schema diagram pdf

** Jon Bartels, fellow programmer who coined the edge cases as “snowflakes”…because everyone wants to be special and unique.

routes.rb maps routes for a Rails app and they are checked in order.  So if we add a route at the end of that list it will assume that the route didn’t match any previous route. Here’s a sample:

map.connect ‘*some_attribute’, :controller => application

Any route that hits this will be sent to the application/index. Here is  simple fix for the index method:

def index
logger.error exception.backtrace.join(”\n”)
render :template => “my_error_page”, :status => :not_found
end

rescue_from ActiveRecord::RecordNotFound do |exception|  logger.error exception.backtrace.join(”\n”)  render :template => “record_not_found”, :status => :not_foundend

API Reference: rescue_from