search for: create_db

...got through the //localhost:3000 information. At that point, I figured I need an app and have been working on salted hash login. I found http://wiki.rubyonrails.com/rails/show/SaltedLoginGeneratorQuickstart and worked through to where I want the create the db tables. Instead, I get script/create_db -bash: script/create_db: Permission denied [root@astarcc html]# ruby script/create_db ./script/../config/../lib/localization.rb:82:in `module_eval'':(eval):3:in `module_eval'': undefined method `render_body'' for class `Class'' (NameError) from ./script/../...

I''m not sure I completely understand the benefits of using ERBSQL or how to use it. Google searches have proved it to be rather undocumented. From what I understand the embedded ruby sql allows you to write sql that''s easier to deploy via the create_db script and also more portable to postgres, myslq, or whatever. But what I can''t find is a resource that explains the preset constants or how to configure them if need be. For example the ERB that comes with the saltedlogingenerator for rails looks like this: CREATE TABLE users (...

...While I can probably sell them on trying Rails, they are definitely going to want the database to sit in our SQL Server instance with our other databases. I can''t get instiki to create the tables in sql server though (I''ve added ADO.rb, and gotten a connection). When I run the create_db script I get the output below. Has anyone tried this? C:\software\instiki-ar>ruby script/create_db C:/software/instiki-ar/script/../config/environment.rb:16: warning: already init ialized constant RAILS_ROOT C:/software/instiki-ar/script/../config/environment.rb:23: warning: already init ializ...

...;'m having a problem requiring resources I''ve defined in other modules. At the moment, I have the following (simplified): /etc/puppet/modules/bacula/manifests/init.pp: class bacula { ... define configure ( $gui="true", $db_password ) { ... postgresql::create_db { "bacula": alias => create_bacula_db, require => create_bacula_user, owner => "bacula", } postgresql::authorise{"bacula": alias => au...

One problem I sort of always had with the ActiveRecord''s tight coupling to the SQL backend is how slow it makes the unit tests. OK, there are some ways to make it faster at a price of extra complexity (reusing the fixtures, doing a rollback in the end of the test, etc), but still - it is much slower than what I would like a unit test to be. Today I had a very simple idea (why, oh why