Ruby/PHP/Lighttpd

Hey guys, I wanted to learn Ruby more precisely Ruby on Rails, and I ran
into some problems hope you all can help. I installed ruby, gems, rails,
php, lighttpd on Fedora Core 4. Tested everything and it is working. As
my config file for Lighttpd I use the one from this
http://www.digitalmediaminute.com/howto/fc4rails/#testLighttpd. I have a
directory /home/leTus/develop where I want to put all my projects. For
example let’s say I have /home/leTus/develop
->/Forum [PHP]
->/Demo [Ruby]
->/project3 [PHP]
Using the config from the tutorial above I added a virtual host for my
Demo project and after adding demo to my /etc/hosts file I can access it
by typing demo in my browser. From my other computer I browse to the
Linux box and I get the Lighttpd welcome screen, but when I type
something like http://demo.192.168.0.103 or http://192.168.0.103/demo I
don’t get anything basically the project is un accessible from another
comp. Another thing is that for every project I’ll have to go to the
hosts file and edit it. Is there a way where I can just make some config
file so I can access my projects this way http://localhost/demo or
http://localhost/Forum and have the php and ruby working. It’s kind of
confusing but I can give more details if anybody is willing to help. i
looked at some tutorials but they are talking about virtual hosts and
stuff.

So nobody can help me?

On 17 Nov 2005, at 19:09, leTus wrote:

config
file so I can access my projects this way http://localhost/demo or
http://localhost/Forum and have the php and ruby working. It’s kind of
confusing but I can give more details if anybody is willing to help. i
looked at some tutorials but they are talking about virtual hosts and
stuff.

Add demo to the hosts file on the other machine then surf to http://
demo/ on it.

Generally people will take longer than 4 and a half hours to check
and answer emails. Don’t give up hope just yet :wink:

Yours,
Craig

Craig W. | t: +44 (0)131 516 8595 | e: [email protected]
Xeriom.NET | f: +44 (0)709 287 1902 | w: http://xeriom.net

these are 2 separate issues. IIS knowing how to “automatically” run
files has nothing to do with your machine being able to resolve the
host “demo”. Its straight up DNS. If you cant “ping demo” from the
command line, then you cant connect to any ports on that machine
either which is why Craig made the suggestion above.

adam

craig wrote:

Add demo to the hosts file on the other machine then surf to http://
demo/ on it.

Generally people will take longer than 4 and a half hours to check
and answer emails. Don’t give up hope just yet :wink:

Yours,
Craig

Craig W. | t: +44 (0)131 516 8595 | e: [email protected]
Xeriom.NET | f: +44 (0)709 287 1902 | w: http://xeriom.net

Yeah but this is exactly what I don’t want to be doing, I want something
like IIS does, all I need to do is to make a directory put my files in
there and IIS automaticaly knows how to run them.

straightflush wrote:

these are 2 separate issues. IIS knowing how to “automatically” run
files has nothing to do with your machine being able to resolve the
host “demo”. Its straight up DNS. If you cant “ping demo” from the
command line, then you cant connect to any ports on that machine
either which is why Craig made the suggestion above.

adam

I don’t thing you all understand what I want, I know I can’t access demo
what I meant is that for every project I am going to make I’ll have to
add a new virtual host and change settings in hosts file also if I
want to access that project from another computer from my network I’ll
have to change the hosts file on that computer too. What I want is to
have my /home/leTus/develop directory as the server root and all the
directories inside of it working no matter what scripting language I
use. For example in develop folder I would have 5 projects 3 PHP and 2
Ruby, and I could access them like this http://localhost/project1,
http://localhost/project2 and so on. And if I want to make a new ruby
project I would go and genereta the new one in the develp folder let’s
say project6 and it would be working without or a little change in the
lighttpd.conf file.