Configure Rails for previous installation of MySQL

I’m “exploring” Ruby and Ruby on Rails. Like what I see so far, but
have one question.

How do I configure Rails for a previous installation of Apache and
MySQL?

I already have both products installed working to my needs and would
like to keep the environment the same.

Previously, I installed Rails using the InstantRails for windows
“bundle” but ran into many errors.

I have installed Rails thru the command line and tried to use the
cookbook example, but keep running into problems. Many windows popping
up with errors from my previous installations.

Help would be appreciated.

Regards,

-jP

Can you be more specific about your MySQL setup? Does your question
pertain to configuring rails to talk to MySQL database (the settings in
‘database.yml’.) or are you talking about how to get rails to use
lagacy tables that following a naming scheme different than rails
assumes? I haven’t yet deployed rails with apache…have been doing all
my testing with webrick, I’m just not at that point yet.

John-Scott wrote:

Can you be more specific about your MySQL setup? Does your question
pertain to configuring rails to talk to MySQL database (the settings in
‘database.yml’.) or are you talking about how to get rails to use
lagacy tables that following a naming scheme different than rails
assumes? I haven’t yet deployed rails with apache…have been doing all
my testing with webrick, I’m just not at that point yet.

John-Scott,

Not quite sure what kind of answer I’m looking for.

When I start my machine up, I see mysqld-nt-exe process running and an
apache.exe process running.

I try to start InstantRails and receive a message box indicating:

MySQL port (3306) is used by “” (mysqld-nt.exe) !

I know that in order for me to use the sample application that comes
with InstantRails (the recipe one), I can’t have these processes
running, but after InstantRails starts up, there are two (2) apache.exe
processes running and one mysqld.exe process running.

I’m probably going to have to dig into the Apache config file for more
answers.

I’ve gotten the sample app to work but if I stop InstantRails and then
start again, I receive a bunch of error message boxes (described below)
and then finally IR starts up.

Warning
Unknown(): (null) Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=1
PHP compiled with module API20020429, debug=0, thread-safety=1
These options need to match

apache.exe - Unable To Locate Componenet
This application has failed to start because DB2CLI.dll was not found.
Re-installating the application may fix this problem.

Warning
Unknown(): Unable to load dynamic library ‘C:\Program
Files\Zend\Core for IBM\lib\phpext\php_ibm_db2.dll’ - The specified
module could not be found.

Warning
Zend Optimizer for PHP 4.3.x cannot be found (expected at
‘C:\Program Files\Zend\Core for
IBM\lib\zend\optimizer\php-4.3.x\ZendOptimizer.dll’) - try reinstalling
the Zend Optimizer

Warning
----- one more message box (tired of writing out meaningless
stuff)

Each of the above messages appear three times in the above sequence.

I’d like to get to the point where I have instant rails using my
typically and previously started processes for apache and mysql.

Actually, I probably need the “complete idiots guide to ruby” for a
absolutely zero level introduction and start there.

Regards,

-jP

If you are just trying to demo or learn rails, you can get rid of the
separately installed Apache/MySQL (unless these are installed for other
reasons). This just adds layers of complexity you don’t need while
trying to get your bearings in rails. If for whatever reasons you want
to stick with the separately installed MySQL/Apache then manually
install rails as instructed at http://rubyonrails.org/down and follow
the configuration instructions for getting rails working with
MySQL/Apache.
You should treat it as an either/or/but-not-both situation…that is,
either go with InstantRails(and the bundled MySQL and Apache) or
manually install Rails/MySQL/Apache separately but don’t try to combine
the two solutions.
It sounds like you are at the early stages of RoR learning. By using
the InstantRails solution, you can skip configuration headaches and
just focus on using/learning rails. By doing things manually, you
introduce layers of complexity to the learning process.
I’m still learning rails and I have deliberately put off trying to
configure rails with Apache because 1) I’m still a good ways off from
being production ready and 2) I don’t need the stress/distraction of
troubleshooting additional configuration stuff while I’m still trying
to learn how to write my own methods.

does this help? or did you get a better idea of what you’re trying to
accomplish in the meantime? let me know.

john-scott