Ron Parker wrote:
>
> I am trying to get a better understanding of my options. I own www.foo.com
> and am serving a midgard site from www.foo.com:8099. I want to test Midhoo
> and would like to do so within www.foo.com. As I see my options, they are;
> www.foo.com:available-range-of-ports or taking the current foo.com:8099
> off-line and replacing it with the new one that will be on-line.
No need, actually. You can try midHoo in a site that allready has a
Midgard
deployment. There isn't (or shouldn't be) anything in midHoo that
depends
on having a host all for itself. Just set up a separate topic tree.
> I don't really need to keep the current foo.com:8099 on-line but if I did
> then serving it from another port is the obvious solution. I am pretty
> ignorant on the topic of ports. Can someone give me a hint in reguards to
> a good range of ports to use for httpd servers? I suppose 8102 would be a
> fair guess.
Anything other that 80 (or 443 for https) is non-standard anyway and
will
require explicit mention of the portnumber in URLs anyway (except for
host-relative links which assume the current host & port). So any pick
is
going to be as good as the other, given that you stay out of the < 1024
range, which is where most standard services live.
> Unfortunately, I haven't gotten my ISP to put "*" in my sub-DNS entries.
> Might have to learn to run my own DNS.
The wildcard doesn't allways work. You can't have
mail.foo.com -> 192.168.1.1
ftp.foo.com -> 192.168.1.2
*.foo.com -> 192.168.1.3
for example. The wildcard setup is an all-or-nothing deal. So maybe that
is
the problem your ISP is seeing.
Bye,
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
