On Jan 20, 4:35�pm, Kyle Wakefield <rails-mailing-l...@andreas-s.net>
That helps a lot! The guide I've been following never actually explained
why port 3000 was to be used, and I never got it working because I had
ignorantly specified port 80 for the Apache virtual host I added. I've
added a new virtual host for development that uses port 3000 and
everything works the way you explained. Thank you for the help, Rob.
This makes development mode SEEM like it works, I can access my app from
port 3000, but when there's an error it gets logged to
config/production.log (so it's not in actually development mode).
When I use the WEBrick server, development mode does work, and errors
are logged to config/development.log. But then I can only view my app at
127.0.0.1. When WEBrick starts it says: "Rails 2.1.0 application started
on http://127.0.0.1:3000"
My questions are:
Does development mode only work with the WEBrick server?
If so, I assume I need to configure it to use an address other than
127.0.0.1?
If not, does someone know what I could be missing in my Apache
configuration that is keeping me from accessing development mode?
Interesting way of doing things, and I'm not 100% sure what your OS
environments on your machines are, but it really is kind of nice to be
able to develop on separate machines with something as simple as "thin
start" on the machine and the using Git to handle the source.