Search Results

Search found 2 results on 1 pages for 'erskingardner'.

Page 1/1 | 1 

• Creating an admin user in Devise on Rails beta 3

  - by erskingardner

  Ok, I'm probably going to feel quite dumb when someone answers this one with a simple thing that I'm missing but... here goes: I've got a brand new app on rails 3 beta and I'm using devise for the authentication. I've run all the comments and everything is working perfectly at the moment. I've created a user role and an admin role (following these instructions: http://wiki.github.com/plataformatec/devise/adding-an-admin-role) and I've registered myself as the first user but how to do I register or create an admin role user? The directions from the devise guys setup the admin role to not be registerable but I'm unsure how you're supposed to create the admin if you can't register?! Any help would be appreciated! Thanks!

  Read the article

• Why does schema.rb change (in the eyes of Git) when just running rake db:migrate?!

  - by erskingardner

  This is a little general I know, but it's been bugging the hell out of me. I've been working on lots of rails projects remotely with Git and every time I do a git pull and see that there is some sort of data change (migration, or schema.rb change) I do a rake db:migrate. These generally run fine and I can continue working. But if you do a git pull and then git status, your working directory is clean (obviously) then do a rake db:migrate (obviously when there are changes) and another git status and all the sudden your db/schema.rb has changed. I have been just doing a git checkout immediately to reset back to the latest committed version of the schema.rb file, but why should this be necessary?! What is rails doing? Updating a timestamp? I can't seem to figure out what the diff is but maybe I'm just missing something?

  Read the article

1