Book- Rails for Java Developers

The link http://www.amazon.com/gp/product/097761669X?tag=jranch-20 talks about 2 sections
-Project automation
-Configuration

Does the first mean building application,running unit test etc.

Yep, we feel pretty strongly that unless the story for managing your project is at least as compelling as for Java, you wouldn't want to switch. That part of the book covers testing (unit, functional, integration, UI), continuous integration, reporting and database management through migrations.

I'm curious as to where you draw the line regarding project automation. I mean, running unit and functional tests is clearly "in" but I guess it wasn't quite so clear cut when you start including more distant aspects. For example, if you talk about continuous integration you need to talk about version control. If you talk about continuous integration and version control, should you talk about database migrations? If you talk about database migrations, should you talk about deployment? If you talk about deployment, should you talk about scaling options?

Based on the description at pragprog.com, it doesn't seem like you discuss Capistrano(?) so I assume that's where the buck stops?

If you talk about continuous integration and version control, should you talk about database migrations?

What is the relation between version control and database migration

Originally posted by Pradip Bhat:
What is the relation between version control and database migration

You do version your database schema along with your source code, don't you?

Originally posted by Lasse Koskela:

You do version your database schema along with your source code, don't you?

ok.

Based on the description at pragprog.com, it doesn't seem like you discuss Capistrano(?) so I assume that's where the buck stops?

What is Capistrano ?

See...

About "Capistrano: Automating Application Deployment

Gian