[Locomotive-users] (persistent?) configuration problems
Rich Morin
rdm at cfcl.com
Tue Jan 30 00:07:32 GMT 2007
At 2:51 PM -0500 1/29/07, Ryan Raaum wrote:
> Open a terminal from locomotive while this app is selected.
> Then from that terminal run:
>
> mongrel_rails start
>
> Are there any obvious error messages there?
> Can you connect to this app?
Although b2's entry in the "Locomotive 2.0.8" window says
it is using port 3003, when I tried this command, I saw:
> Last login: Sun Jan 28 16:19:17 on ttyp2
> source /private/var/tmp/folders.1000/TemporaryItems/
> 8EC7BD24-AFF4-11DB-B0AE-000A95D321F2-4337-
> 000006DFA4911A5A.environment.csh
> Welcome to Darwin!
> [libre:~] rdm% source /private/var/tmp/folders.1000/TemporaryItems/
> 8EC7BD24-AFF4-11DB-B0AE-000A95D321F2-4337-
> 000006DFA4911A5A.environment.csh
> [libre:~/Boswell/b2] rdm% mongrel_rails start
> /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/
> powerpc/bin/mongrel_rails:17:Warning:
> require_gem is obsolete. Use gem instead.
> ** Starting Mongrel listening at 0.0.0.0:3000
> ** Starting Rails with development environment...
> /Users/rdm/Boswell/b2/config/boot.rb:29:Warning:
> require_gem is obsolete. Use gem instead.
> ** Rails loaded.
> ** Loading any Rails specific GemPlugins
> ** Signals ready. TERM => stop. USR2 => restart.
> INT => stop (no restart).
> ** Rails signals registered. HUP => reload (without restart).
> It might not work well.
> ** Mongrel available at 0.0.0.0:3000
> ** Use CTRL-C to stop.
That is, Mongrel decided to use port 3000. So, I tried to
connect to port 3000 and succeeded.
Should I nuke the caches and plists that Ray Baxter noted?
-r
--
http://www.cfcl.com/rdm Rich Morin
http://www.cfcl.com/rdm/resume rdm at cfcl.com
http://www.cfcl.com/rdm/weblog +1 650-873-7841
Technical editing and writing, programming, and web development
More information about the Locomotive-users
mailing list