[Instantrails-users] Conflict with currently running MySQL instance

Ken Barker ken.barker at gmail.com
Wed Oct 12 15:43:11 EDT 2005


On 10/12/05, Curt Hibbs <curt.hibbs at gmail.com> wrote:
>
> Do you really want/need to be running more than one instance of MySQL? You
> could just continue to use the one you already have and not use the one in
> Instant Rails. To do that you would use the menu command "Configure >>
> Instant Rails" and then uncheck the box that labelled "Automatically start
> the servers when Instant Rails starts".
>
> Of course this will stop apache from automatically starting, too. You can
> manually start it by clicking on the Apaqche button and selecting "Start".
> Maybe in the next release I should have separate options for auto-starting
> apache and mysql.
>
> You could also move your MySQL data into the Instant Rails instance and
> just run that one.
>
> If you *really, really* want to run two instances of MySQL simultaneously,
> I'd need to do a little research to see what the implications would be.
> Obviously it'd have to run on a different port, and somehow you'd have to
> tell Rails about this.
>
> Unfortunately, between work and getting ready for RubyConf, I really don't
> have time to look into this right now.
>

No urgency here. Just excited about Instant Rails and eager to give you
feedback. I have no rock solid reasons for running two MySQL instances. Just
so happened that I had my regular setup running when I tried Instant Rails.

Thank you and enjoy RubyConf.

Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/instantrails-users/attachments/20051012/96f74dbe/attachment.htm


More information about the Instantrails-users mailing list