m2sh command help ambiguity
- From:
- Eimantas Vaiciunas
- Date:
- 2011-07-03 @ 19:41
Hi all
It appears that I have been misinterpretting the help of `m2sh start`
command thinking that each host can be started/stopped separately
while `m2sh help` near the line of `start` command stated that it
starts only the server.
While using M2 in my local machine I always thought I can start stop
separate hosts. I.e. make mongrel2 respond to their dns names
depending on whether they are started or stopped. It appears that it's
not like that. And I've learned it the hard way. Scenario:
"I have misinterperted the m2sh command help and I think I can make
mongrel2 respond to host names depending on whether I 'start' or
'stop' them".
1) configure host1 which is a simple statically generated image
gallery (Host() to Dir()).
2) start the site with `m2sh start -host host1`
3) configure host2 which is a handler for fetching weather information
from 3rd party website.
4) load the new config
5) by my misinterpretation I "start" the new host with `m2sh start -host host2`.
6) see errors on the screen about unavailable socket.
7) try stopping the host2 with command `m2sh stop -host host2`
At this point I see that host1 is down and is not responding to
requests. After that I get the point that `m2sh help` command is more
accurate. I'm just probably missing something so I'd like to ask -
what is the motivation behind providing the -host parameter to `m2sh
start` command?
// E.