ActiveState Community Site - rails - Comments

Mainly because I develop on

webPragmatist — Thu, 20 Mar 2008 17:19:32 -0700

Mainly because I develop on many different machines.

The PythonRemoteDebugging package is only for Python

ericp — Thu, 20 Mar 2008 12:14:30 -0700

For Ruby debugging, you only need these files:

[komodo-install-dir]/.../support/dbgp/rubylib
  rdbgp.rb
  rdbgp/
  1.8/ *** Optional -- should be installed with 'gem install ruby-debug-base'

Since you copied the above directory from a Windows machine to a Linux one,
you can't use the binary libraries in the 1.8/ directory -- they were
built for Windows only. Please delete the whole 1.8 directory on your Linux machine.

Then follow the instructions in
[Help|Debugging|Debugging Ruby|Debugging Ruby Remotely]

Generating Ruby projects remotely is way beyond the scope of the tutorial and screencasts I've done. Why not build and develop them locally, and deploy remotely?

Regards,
Eric

Ok.. I am somewhat understanding this :)

webPragmatist — Thu, 20 Mar 2008 04:34:25 -0700

Here's what I have done (I hope this helps others):

Copied the dbgp folder from C:\Program Files\ActiveState Komodo IDE 4\lib\support\dbgp to my Linux home directory ~/Komodo/dbgp/
Downloaded the Komodo-PythonRemoteDebugging package and overwrote ~/Komodo/dbgp/bin and ~/Komodo/dbgp from that package (it also put some files in ~/Komodo/)
Made sure port 9000 was set in Preferences>Debugger>Connection
Ran export RUBYDB_OPTS=remoteport=my.domain.com:9000 in my rails application folder
Ran ruby -I/home/username/komodo/dbgp/rubylib/ -r /home/username/komodo/dbgp/rubylib/rdbgp.rb script/server in my rails application folder
Ran sudo gem install ruby-debug-base as per the below error message suggests

I still get the error:

Error: /home/username/komodo/dbgp/rubylib/1.8/ruby_debug.so: invalid ELF header - /home/username/komodo/dbgp/rubylib/1.8/ruby_debug.so

The Komodo ruby debugger couldn't load the ruby-debug-base component.
  This library ships with Komodo, but also can be installed by running `gem install ruby-debug-base'

The documentation isn't really clear what to do with the Komodo-PythonRemoteDebugging package once you download it, so I guessed.

Thanks for your help in advance. Oh, and you didn't say whether this would allow new ruby projects to be generated remotely (as the tutorial demonstrates) using rails .

Remote rails debugging in a nutshell

ericp — Tue, 18 Mar 2008 15:29:09 -0700

This is untested, but here's how I would do it:

Let's assume you're running Komodo on a Windows box called "buckley.acme.com".
Go into Preferences|Debugger|Connection and have it listen on the
specific port 9000, or whatever port is handy. Make sure
the menu item Debug|Listen for Debugging Connections is checked.

On the Linux box, move to the directory containing the file rdbgp.rb,
the main Komodo Ruby debugger file. Run this shell command:

% rdbg=`pwd`

The only reason to do this is because that path is often very
long. We need to type that path twice, in the next command,
so typing four characters going to be easier to read. If you're
going to do this kind of debugging often you might as well give
the variable a more meaningful name and set it in your profile.

Now move to the directory containing your Ruby script, and run
these commands:

% export RUBYDB_OPTS=remoteport=buckley.acme.com:9000
% ruby -I$rdbg -r $rdbg/rdbgp.rb script/server webrick

That should do it.

All of what is in the help

webPragmatist — Tue, 18 Mar 2008 14:48:59 -0700

All of what is in the help file is pretty much greek because it doesn't explain what exactly you are installing...

So, I got to "install Komodo-PythonRemoteDebugging" and then thought, how in the world is it going to know how to connect to the server with SSH?

Plus, all I am interested in right now is the scripts... does the debugger even do this (like how komodo will run > rails project_name <?

I've assumed Rails work is best done locally

ericp — Tue, 18 Mar 2008 13:24:13 -0700

I'm still learning about deployment, which is obviously done on a remote machine. I'd rather run tests remotely than fire up the debugger. You could use Komodo to remotely debug a remote Rails app, but you'd have to configure the remote app first -- see

Help|Debugging|Debugging Ruby|Debugging Ruby Remotely

for an idea of how to go about this.

Remote Development?

webPragmatist — Tue, 18 Mar 2008 13:06:30 -0700

Hey eric nice job on the video (am still watching),

As I try to follow along I am curious to see how this would work with a remote environment (over SSH ideally so that the rails scripts can be run).

Any insite as to how to go about this?

Answering the question about listing attributes (finally)

ericp — Wed, 20 Feb 2008 14:05:30 -0800

You don't have to list all the attributes in the scaffold command.
The scaffold command will auto-generate the created_on and updated_on
timestamp fields for you automatically. You can bypass that by
running the command from the command-line, like so:

ruby script/generate scaffold --skip-timestamps ModelName attr:type ...

Later on you would use the generate/migration and
migrate/db:migrate commands to add more attributes,
just like in 1.x.

You should be able to add new attributes incrementally

ericp — Tue, 05 Feb 2008 10:31:42 -0800

You'll have to manually update the views, but scaffold-generated
views have always been intended to be just scaffolding, and not
the final product.

As I showed above, I find the controllers that the new
scaffolder generates to be pretty cool.

Scaffolding changed with Rails 2.0

ericp — Tue, 05 Feb 2008 10:25:42 -0800

The changes are not backward-compatible, unfortunately.
I couldn't resist showing some of the benefits of
the new version, while showing how to get going...

The new site for the scaffold-resource-generated app is:

http://localhost:3000/movies/

Because the scaffold generator is now restful it gives you
the following URIs:

http://localhost:3000/movies/ ==> index

http://localhost:3000/movies/3 ==> display item 3

http://localhost:3000/movies/4/edit ==> edit page for item 4

http://localhost:3000/movies/new ==> display new-movie page

And you can add a ".xml" to the end of the URL:

http://localhost:3000/movies/2.xml ==> return an XML view of item 2

Now add this line to the show method in movies_controller.rb,
under the format.xml line:

format.js { render :json => @movie }

format.js { render :json => @movie }

Here's what the JSON Rails returns would look like.

$ wget -q  -O - http://localhost:3000/movies/2.js
{"updated_at": "2008/02/05 10:15:21 -0800",
 "title": "elf",
 "id": 2,
 "year": 2002, "created_at": "2008/02/05 10:15:21 -0800"}
$

Hope this gets you going. I plan on updating the toolset and
screencast to work with Rails 2 soon now.

How many Attributes do you have to list?

PogiNate — Tue, 05 Feb 2008 09:53:16 -0800

Do you have to list all attributes of the model, or does this let you create a scaffold selectively? Also, what is the address for the scaffold once it's created? According to the tutorial, it should be http://localhost:3000/library, but clearly it's not going to get the library name now.
:Nate Dickson

customizations

bVs — Mon, 25 Jun 2007 16:59:04 -0700

plz provide any useful snippets, macros you might have created for your screencast...
maybe some of them are good for general use

------edited------
yes, i found them in the IDE, however one's own snippets are 'handier' rather than default...

They all ship with Komodo 4.1, both Edit and IDE

ericp — Mon, 25 Jun 2007 10:48:31 -0700

I don't recall using any custom snippets or macros in the screencast,
just the ones that come with the Ruby on Rails Project Template.

I actually used more snippets and macros in the thirty minute version
of that screencast, which for obvious reasons we scrapped.

Would a screencast on snippets and macros alone be useful?

Enjoyed the Rails screencast

minkley — Thu, 21 Jun 2007 17:05:41 -0700

I have not played with Ruby yet .. I will definitely be taking a look after watching the screencast.

Screencast length is 15m47s

ErinW — Thu, 21 Jun 2007 15:58:58 -0700

In case you were curious before launching.