Comments on: Ruby out of the Rails – Nitro and Og http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/ Just a little about development! Think before you write! Tue, 08 Dec 2009 10:19:55 -0200 http://wordpress.org/?v=2.8.5 hourly 1 By: George Moschovitis http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-110 George Moschovitis Sat, 27 Oct 2007 16:36:19 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-110 You need to set both to false :create_schema => false, :evolve_schema => false, you enable these options only in development (or whn you want to actually update your schema on the live server (and have previously tested this in your debug/staging server) You need to set both to false

:create_schema => false,
:evolve_schema => false,

you enable these options only in development (or whn you want to actually update your schema on the live server (and have previously tested this in your debug/staging server)

]]> By: Robert Mela http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-108 Robert Mela Sat, 27 Oct 2007 02:10:44 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-108 My guess was wrong -- looks like it's :create_schema that needs to be disabled. Og.start( :name => 'mydb', :create_schema => false .... ) My guess was wrong — looks like it’s :create_schema that needs to be disabled.

Og.start( :name => ‘mydb’, :create_schema => false …. )

]]> By: Robert Mela http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-106 Robert Mela Fri, 26 Oct 2007 20:56:30 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-106 My guess would be Og.evolve_schema = false, or adding :evolve_schema => false to the option hash of Og.start, e.g. Og.evolve_schema = false or Og.start( :name => "booklist", :adapter => :sqlite, :evolve_schema => false ) See the slowly evolving cheatsheets at http://robmela.com/cheatsheets My guess would be Og.evolve_schema = false, or adding :evolve_schema => false to the option hash of Og.start, e.g.

Og.evolve_schema = false

or

Og.start( :name => “booklist”,
:adapter => :sqlite,
:evolve_schema => false )

See the slowly evolving cheatsheets at http://robmela.com/cheatsheets

]]> By: Urubatan http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-103 Urubatan Fri, 26 Oct 2007 19:53:44 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-103 thanks for the tips, I'll test it again and will write another post about it :D PS.: I do not like very much the auto schema update option (did not know nitro has it, but now that i know, is there a way to disable it?), I have had lots of troubles with this kind of feature in hibernate (Java), a migration enables me to write code that for example, moves the data to a new column, process it some way, and then add it to the new column, instead of simply creating a new column with the default value ... thanks for the tips, I’ll test it again and will write another post about it :D

PS.: I do not like very much the auto schema update option (did not know nitro has it, but now that i know, is there a way to disable it?), I have had lots of troubles with this kind of feature in hibernate (Java), a migration enables me to write code that for example, moves the data to a new column, process it some way, and then add it to the new column, instead of simply creating a new column with the default value …

]]> By: Arne http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-101 Arne Fri, 26 Oct 2007 17:43:32 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-101 I don't know where how you got the impression that automatic reloading of code doesn't work.Over here it works flawless. Only when you change app.rb itself do you need to restart to server. The directory layout that nitro --create generates is considered canonical. You're free to deviate, but all current examples will use this layout. To get automatic loading of ruby files without having to explicitly require them just add something like Dir['app/**/*.rb'].each{|f| require f} to your app.rb. Thank you for trying out Nitro! I don’t know where how you got the impression that automatic reloading of code doesn’t work.Over here it works flawless. Only when you change app.rb itself do you need to restart to server.

The directory layout that nitro –create generates is considered canonical. You’re free to deviate, but all current examples will use this layout. To get automatic loading of ruby files without having to explicitly require them just add something like

Dir['app/**/*.rb'].each{|f| require f}

to your app.rb.

Thank you for trying out Nitro!

]]> By: Robert Mela http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-98 Robert Mela Fri, 26 Oct 2007 13:53:35 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-98 The ability to put things wherever you like comes in addition, not instead of. There is a bin/nitro command that lays out a canonical standard directory hierarchy, but it's also simple enough that after the first week I could create it from memory. nitro --create myapp results in myapp ( locate main application script here ) myapp/app/models myapp/app/controllers myapp/app/conf myapp/app/templates myapp/app/public myapp/app/public/css myapp/app/public/css/js The freedom to do tiny experiments with a minimal layout of one or two files has been incredibly useful. I still have the canonical structure for more significant projects. The ability to put things wherever you like comes in addition, not instead of.

There is a bin/nitro command that lays out a canonical standard directory hierarchy, but it’s also simple enough that after the first week I could create it from memory.

nitro –create myapp

results in

myapp ( locate main application script here )
myapp/app/models
myapp/app/controllers
myapp/app/conf
myapp/app/templates
myapp/app/public
myapp/app/public/css
myapp/app/public/css/js

The freedom to do tiny experiments with a minimal layout of one or two files has been incredibly useful. I still have the canonical structure for more significant projects.

]]> By: George Moschovitis http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/comment-page-1/#comment-97 George Moschovitis Fri, 26 Oct 2007 13:24:01 +0000 http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/#comment-97 Thanks for trying out Nitro. I would advise you to grab the (vastly improved) repository version and join the mailing list for extra help. I really think that Nitro is actually simpler to use than Rails. For example Og does not need migrations because it provides automagic database evolution. If you change your ruby classes and restart your application, Og automatcially detects the changes and alters the database schema accordingly (ie adds columns/ removes columns, alters columns etc). Thanks for trying out Nitro. I would advise you to grab the (vastly improved) repository version and join the mailing list for extra help. I really think that Nitro is actually simpler to use than Rails.

For example Og does not need migrations because it provides automagic database evolution. If you change your ruby classes and restart your application, Og automatcially detects the changes and alters the database schema accordingly (ie adds columns/ removes columns, alters columns etc).

]]>