search for: elliottg

I have a migration "x" that when it runs self.up it adds a new column to a table, and of course when self. down is run it deletes said table... After I ran this migration I continued to work and in the process added a couple other migrations. After a while I realized that the column migration "x" created was a mistake and I no longer need it. So I ran rake db:migrate:down

I have a few custom generators within ~/.rails/generators. This works fine and they all show up under "User" as they should when I run script/generate. I would like to be able to have multiple Dirs. under ~/.rails/ generators so I can better organize things and have unique repos for each. If I do something like ~/.rails/generators/cms_generators/gen_1 and

I am working on a Gem that has several Gem dependencies of its own. The Gem''s .gemspec looks good (I think) and when "bundle install" is called from the parent app, it lists that it is indeed "Using" the Gem''s required Gems. I''ll refrain from an Inception analogy here ;) When I fire up the app and make a request, I get "uninitialized constant